Fix some broken external links

lychee.toml

@@ -88,6 +88,7 @@ headers = []
 # The balena/resin API urls will not respond to unauthenticated requests
 # The gstatic and googleapis links go 404 and are excluded ever since we started checking HTML
 # balenaCLI linux binary URLs always error out since they are generated on run time only
+# admin.google.com/ac/apps/unified always redirects to login 
 # File URLs are excluded as they aren't checked properly and error out
 exclude = [
     "https://github.com/balena-io-library/base-images",
@@ -118,9 +119,10 @@ exclude = [
     "https://www.googletagmanager.com/gtm.js?*",
     "https://github.com/balena-io/docs/issues/new?*",
     "https://api/",
-    "https://raw.githubusercontent.com/balena-os/meta-balena/$%7Bos_version_tag%7D/meta-balena-common/recipes-containers/balena-supervisor/balena-supervisor.inc",
+    "https://raw.githubusercontent.com/balena-os/meta-balena/[^/]+/meta-balena-common/recipes-containers/balena-supervisor/balena-supervisor.inc",
     ".gitbook/assets/",
-    "^[^http]"
+    "^[^http]",
+    "https://admin.google.com/ac/apps/unified"
     ]
 
 # Exclude these filesystem paths from getting checked.

pages/faq/troubleshooting/var-som-mx6.md

@@ -31,7 +31,7 @@ If you have an HDMI screen attached, you should see balena logo on the screen wh
 
 ### Detailed provisioning instructions
 
-Currently balenaOS on the Variscite VAR-SOM-MX6 is only capable of booting from SD card, but in the future [eMMC booting will be supported](https://github.com/balena-os/resin-imx6ul-var-dart/issues/64). To provision the device, do the following:
+Currently balenaOS on the Variscite VAR-SOM-MX6 is only capable of booting from SD card, but in the future [eMMC booting will be supported](https://github.com/balena-os/balena-variscite/issues/64). To provision the device, do the following:
 
 1. Verify Switch SW5 is OFF (downwards).
 2. Set Boot select switch (SW6) right to boot from microSD Card.

pages/learn/develop/cloud-iot-provisioning/aws.md

@@ -11,7 +11,7 @@ Our IoT provisioning tools automate device registration to AWS IoT Core, and lev
 Provisioning includes three components:
 
 * **Service Container** like [Cloud Relay block](https://github.com/balena-io-examples/cloud-relay) on a device to request the provisioning and use the credential environment variables from balenaCloud
-* **Lambda (cloud) function** to securely validate device identity and register the device with IoT Core, triggered by an HTTP request ([source code](https://github.com/balena-io-examples/%7B%7B$cloud.provisionRepoName%7D%7D/blob/master/index.js))
+* **Lambda (cloud) function** to securely validate device identity and register the device with IoT Core, triggered by an HTTP request ([source code](https://github.com/balena-io-examples/aws-iot-provision/blob/master/index.js))
 * **balenaCloud** to accept and store the generated key/certificate credentials for the device
 
 The cloud function first validates the device UUID in the provision request with balenaCloud. Then it generates a public key certificate and registers with the IoT Core service. The function then provides the generated credentials to balenaCloud, which stores and pushes them to the device as environment variables for use by the service container.

pages/learn/develop/cloud-iot-provisioning/azure.md

@@ -11,7 +11,7 @@ Our IoT provisioning tools automate device registration to Azure IoT Hub, and le
 Provisioning includes three components:
 
 * **Service Container** like [Cloud Relay block](https://github.com/balena-io-examples/cloud-relay) on a device to request the provisioning and use the credential environment variables from balenaCloud
-* **Azure (cloud) function** to securely validate device identity and register the device with IoT Hub, triggered by an HTTP request ([source code](https://github.com/balena-io-examples/%7B%7B$cloud.provisionRepoName%7D%7D/blob/master/index.js))
+* **Azure (cloud) function** to securely validate device identity and register the device with IoT Hub, triggered by an HTTP request ([source code](https://github.com/balena-io-examples/azure-iot-provision/blob/master/index.js))
 * **balenaCloud** to accept and store the generated key/certificate credentials for the device
 
 The cloud function first validates the device UUID in the provision request with balenaCloud. Then it generates a public key certificate and registers with the IoT Hub service. The function then provides the generated credentials to balenaCloud, which stores and pushes them to the device as environment variables for use by the service container.

pages/learn/develop/cloud-iot-provisioning/cb-gcp.md

@@ -11,7 +11,7 @@ Our IoT provisioning tools automate device registration to ClearBlade IoT Core,
 Provisioning includes three components:
 
 * **Service Container** like [Cloud Relay block](https://github.com/balena-io-examples/cloud-relay) on a device to request the provisioning and use the credential environment variables from balenaCloud
-* **Cloud  function** to securely validate device identity and register the device with IoT Core, triggered by an HTTP request ([source code](https://github.com/balena-io-examples/%7B%7B$cloud.provisionRepoName%7D%7D/blob/master/index.js))
+* **Cloud  function** to securely validate device identity and register the device with IoT Core, triggered by an HTTP request ([source code](https://github.com/balena-io-examples/cb-gcp-iot-provision/blob/master/index.js))
 * **balenaCloud** to accept and store the generated key/certificate credentials for the device
 
 The cloud function first validates the device UUID in the provision request with balenaCloud. Then it generates a public key pair and registers with the IoT Core service. The function then provides the generated credentials to balenaCloud, which stores and pushes them to the device as environment variables for use by the service container.

pages/learn/manage/actions.md

@@ -76,7 +76,7 @@ Balena currently exposes **port 80** for web forwarding. This setting enables we
 
 The Public Device URL feature is a tool for remote configuration, debugging, and other intermittent or periodic use cases. The feature is built on [Cloudlink](../welcome/security.md#cloudlink) and not designed for high availability. We do not recommend using the Public Device URL feature for continuous use as part of your application.
 
-For applications that require a stable, continuously available public endpoint, we recommend using a dedicated tunneling service designed for production use. Popular services include [Cloudflare Tunnels](https://www.cloudflare.com/products/tunnel/) (See our [blog post](https://www.balena.io/blog/expose-your-balena-device-to-the-internet-with-cloudflare-tunnel/), [Tailscale](https://tailscale.com/) and [Ngrok](https://ngrok.com/).
+For applications that require a stable, continuously available public endpoint, we recommend using a dedicated tunneling service designed for production use. Popular services include [Cloudflare Tunnels](https://www.cloudflare.com/products/tunnel/) (See our [blog post](https://blog.balena.io/how-to-expose-your-device-with-a-custom-url-using-cloudflare-tunnels/), [Tailscale](https://tailscale.com/) and [Ngrok](https://ngrok.com/).
 
 <figure><img src="../../.gitbook/assets/toggle-public-url.webp" alt=""><figcaption></figcaption></figure>
 

templates/cloud-iot-provisioning.md

@@ -11,7 +11,7 @@ Our IoT provisioning tools automate device registration to {{ $cloud.shortName }
 Provisioning includes three components:
 
 * **Service Container** like [Cloud Relay block](https://github.com/balena-io-examples/cloud-relay) on a device to request the provisioning and use the credential environment variables from balenaCloud
-* **{{ $cloud.cloudFunctionName }} {{#isnt $cloud.cloudFunctionName "Cloud"}}(cloud){{/isnt}} function** to securely validate device identity and register the device with {{ $cloud.iotCoreName }}, triggered by an HTTP request ([source code](https://github.com/balena-io-examples/%7B%7B$cloud.provisionRepoName%7D%7D/blob/master/index.js))
+* **{{ $cloud.cloudFunctionName }} {{#isnt $cloud.cloudFunctionName "Cloud"}}(cloud){{/isnt}} function** to securely validate device identity and register the device with {{ $cloud.iotCoreName }}, triggered by an HTTP request ([source code](https://github.com/balena-io-examples/{{ $cloud.provisionRepoName}}/blob/master/index.js))
 * **balenaCloud** to accept and store the generated key/certificate credentials for the device
 
 The cloud function first validates the device UUID in the provision request with balenaCloud. Then it generates a {{ $cloud.credentialType }} and registers with the {{ $cloud.iotCoreName }} service. The function then provides the generated credentials to balenaCloud, which stores and pushes them to the device as environment variables for use by the service container.

templates/troubleshooting/var-som-mx6.md

@@ -1,6 +1,6 @@
 ### Detailed provisioning instructions
 
-Currently balenaOS on the {{ $device.name }} is only capable of booting from SD card, but in the future [eMMC booting will be supported](https://github.com/balena-os/resin-imx6ul-var-dart/issues/64). To provision the device, do the following:
+Currently balenaOS on the {{ $device.name }} is only capable of booting from SD card, but in the future [eMMC booting will be supported](https://github.com/balena-os/balena-variscite/issues/64). To provision the device, do the following:
 
 1. Verify Switch SW5 is OFF (downwards).
 2. Set Boot select switch (SW6) right to boot from microSD Card.