Rename to .com TLD

alexellis · alexellis · commit 5675d6872a0b · 2024-08-06T14:23:50.000+01:00
Signed-off-by: Alex Ellis (OpenFaaS Ltd) &lt;alexellis2@gmail.com&gt;
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -6,7 +6,7 @@
 ## Motivation and Context
 <!--- Why is this change required? What problem does it solve? -->
 <!--- If it fixes an open issue, please link to the issue here. -->
-- [ ] I have raised an issue to propose this change ([required](https://github.com/self-actuated/docs.actuated.dev/blob/master/CONTRIBUTING.md))
+- [ ] I have raised an issue to propose this change ([required](https://github.com/self-actuated/docs.actuated.com/blob/master/CONTRIBUTING.md))
 
 ## How Has This Been Tested?
 <!--- Please describe in detail how you tested your changes. -->
diff --git a/.github/workflows/publish.yaml b/.github/workflows/publish.yaml
@@ -18,7 +18,7 @@ jobs:
         # Or use mhausenblas/mkdocs-deploy-gh-pages@nomaterial to build without the mkdocs-material theme
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          CUSTOM_DOMAIN: docs.actuated.dev
+          CUSTOM_DOMAIN: docs.actuated.com
           CONFIG_FILE: ./mkdocs.yml
           EXTRA_PACKAGES: build-base
           # GITHUB_DOMAIN: github.myenterprise.com
diff --git a/docs/dashboard.md b/docs/dashboard.md
@@ -76,12 +76,12 @@ This is where you get to learn who is trigger the most amount of builds, who may
 
 For up to 120 days of history, you can find jobs that have increased over 5 minutes in duration week-by-week. This feature was requested by a team whose builds were roughly 60 minutes each on GitHub's hosted runners, and 20 minutes each on actuated. They didn't want those times to creep up without it being noticed and rectified.
 
-![Insights on outliers](https://actuated.dev/images/2024-03-cncf-update/outliers-top.png)
+![Insights on outliers](https://actuated.com/images/2024-03-cncf-update/outliers-top.png)
 > Insights on outliers showing the time that the job increased by, and a button to drill down into the affected jobs that week.
 
 When you click "Inspect", a plot will be drawn with the maximum build time recorded on the days of the affected week. You can then click "View Job" to see what commit, Pull Request, or configuration change may have caused the increase.
 
-![A plot with the longest job run on each day of the affected week](https://actuated.dev/images/2024-03-cncf-update/detail-plot.png)
+![A plot with the longest job run on each day of the affected week](https://actuated.com/images/2024-03-cncf-update/detail-plot.png)
 > A plot with the longest job run on each day of the affected week
 
 ## SSH Sessions
diff --git a/docs/examples/github-actions-cache.md b/docs/examples/github-actions-cache.md
@@ -89,4 +89,4 @@ The `path` parameter is used to set the paths on the runner to cache or restore.
 ## Further reading
 
 * Checkout the list of `actions/cache` [examples](https://github.com/actions/cache/blob/main/examples.md) to configure caching for different languages and frameworks.
-* See our blog: [Make your builds run faster with Caching for GitHub Actions](https://actuated.dev/blog/caching-in-github-actions)
+* See our blog: [Make your builds run faster with Caching for GitHub Actions](https://actuated.com/blog/caching-in-github-actions)
diff --git a/docs/examples/kvm-guest.md b/docs/examples/kvm-guest.md
@@ -94,4 +94,4 @@ The full example is available on [GitHub](https://github.com/skatolo/nested-fire
 
 For more examples and use-cases see:
 
-- [How to run a KVM guest in your GitHub Actions](https://actuated.dev/blog/kvm-in-github-actions)
+- [How to run a KVM guest in your GitHub Actions](https://actuated.com/blog/kvm-in-github-actions)
diff --git a/docs/examples/multiarch-buildx.md b/docs/examples/multiarch-buildx.md
@@ -130,7 +130,7 @@ Using QEMU can be slow at times, especially when building an image for Arm using
 
 We found that we could increase an Open Source project's build time by 22x - from ~ 36 minutes to 1 minute 26 seconds.
 
-See also [How to make GitHub Actions 22x faster with bare-metal Arm](https://actuated.dev/blog/native-arm64-for-github-actions)
+See also [How to make GitHub Actions 22x faster with bare-metal Arm](https://actuated.com/blog/native-arm64-for-github-actions)
 
 To build a separate image for Arm on an Arm runner, and one for amd64, you could use a [matrix build](/examples/matrix).
 
diff --git a/docs/faq.md b/docs/faq.md
@@ -55,18 +55,18 @@ For GitHub users, a GitHub organisation is required for installation, and runner
 
 ## Is there a sponsored subscription for Open Source projects?
 
-We have a sponsored program with the CNCF and Ampere for various Open Source projects, you can find out more here: [Announcing managed Arm CI for CNCF projects](https://actuated.dev/blog/arm-ci-cncf-ampere).
+We have a sponsored program with the CNCF and Ampere for various Open Source projects, you can find out more here: [Announcing managed Arm CI for CNCF projects](https://actuated.com/blog/arm-ci-cncf-ampere).
 
 Sponsored projects are required to [add our GitHub badge](/images/actuated-badge.png) to the top of their README file for each repository where the actuated is being used, along with any other GitHub badges such as build status, code coverage, etc.
 
 ```md
-[![Arm CI sponsored by Actuated](https://img.shields.io/badge/SA_actuated.dev-004BDD)](https://actuated.dev/)
+[![Arm CI sponsored by Actuated](https://img.shields.io/badge/SA_actuated.com-004BDD)](https://actuated.com/)
 ```
 
 or
 
 ```html
-<a href="https://actuated.dev/"><img alt="Arm CI sponsored by Actuated" src="https://docs.actuated.dev/images/actuated-badge.png" width="120px"></img></a>
+<a href="https://actuated.com/"><img alt="Arm CI sponsored by Actuated" src="https://docs.actuated.com/images/actuated-badge.png" width="120px"></img></a>
 ```
 
 For an example of what this would look like, see the [inletsctl project README](https://github.com/inlets/inletsctl).
@@ -340,7 +340,7 @@ If you only needed to run Arm builds from 9-5pm, you could absolutely delete the
 
 Yes, both for GitHub and GitLab CI.
 
-See also: [Accelerate GitHub Actions with dedicated GPUs](https://actuated.dev/blog/gpus-for-github-actions)
+See also: [Accelerate GitHub Actions with dedicated GPUs](https://actuated.com/blog/gpus-for-github-actions)
 
 ## Can Virtual Machines be launched within a GitHub Action?
 
@@ -350,7 +350,7 @@ Use-cases may include: building and snapshotting VM images, running Packer, laun
 
 It's disabled by default, but you can opt-in to the feature by following the steps in this article:
 
-[How to run a KVM guest in your GitHub Actions](https://actuated.dev/blog/kvm-in-github-actions)
+[How to run a KVM guest in your GitHub Actions](https://actuated.com/blog/kvm-in-github-actions)
 
 At time of writing, only Intel and AMD CPUs support nested virtualisation.
 
diff --git a/docs/install-agent.md b/docs/install-agent.md
@@ -9,7 +9,7 @@ actuated is split into three parts:
 All we need you to do is to install our agent on one or more servers, then we take care of the rest. We'll even be able to tell you if your server goes offline for any reason.
 
 !!! info "Have you registered your organisation yet?"
-    Before you can add an agent, you or your GitHub organisation admin will need to install the: [Actuated GitHub App](https://docs.actuated.dev/register/#install-the-github-app).
+    Before you can add an agent, you or your GitHub organisation admin will need to install the: [Actuated GitHub App](https://docs.actuated.com/register/#install-the-github-app).
 
 ### Pick your Actuated Servers
 
diff --git a/docs/roadmap.md b/docs/roadmap.md
@@ -43,9 +43,10 @@ Shipped
 * [x] Examples for using S3/Minio running on the server as an actions cache, instead of the default hosted cache within Azure
 * [x] Specify a custom runner size for an individual workflow - i.e. `actuated-8cpu-12gb`
 * [x] Specify `actuated-any` to run jobs on any available server whether amd64 or arm64, for architecture-agnostic workflows such as npm or for browser testing. 
-* [x] GPU pass-through for ML and AI workloads - [Accelerate GitHub Actions with dedicated GPUs](https://actuated.dev/blog/gpus-for-github-actions) - [Run AI models with ollama in CI with GitHub Actions](https://actuated.dev/blog/ollama-in-github-actions)
+* [x] GPU pass-through for ML and AI workloads - [Accelerate GitHub Actions with dedicated GPUs](https://actuated.com/blog/gpus-for-github-actions) - [Run AI models with ollama in CI with GitHub Actions](https://actuated.com/blog/ollama-in-github-actions)
 * [x] Linux Kernel 6.1 for 64-bit Arm
-* [x] Burst above subscription concurrency for busy periods - [Introducing burst billing and capacity for GitHub Actions](https://actuated.dev/blog/burst-billing-capacity)
+* [x] Burst above subscription concurrency for busy periods - [Introducing burst billing and capacity for GitHub Actions](https://actuated.com/blog/burst-billing-capacity)
+* [x] Acquisition of actuated.com TLD
 
 In progress:
 
@@ -75,7 +76,7 @@ Is there something else you need? If you're already a customer, contact us via [
 
 ## Actuated for GitLab
 
-[Learn about the tech preview](https://actuated.dev/blog/secure-microvm-ci-gitlab)
+[Learn about the tech preview](https://actuated.com/blog/secure-microvm-ci-gitlab)
 
 Ready for use by customers:
 
diff --git a/docs/tasks/cli.md b/docs/tasks/cli.md
@@ -4,7 +4,7 @@ Monitor Actuated runners and jobs from the command line.
 
 ## Installation
 
-Download and installation instruction are available via the [actuated-dashboard](https://dashboard.actuated.dev/cli)
+Download and installation instruction are available via the [actuated-dashboard](https://dashboard.actuated.com/cli)
 
 You'll need to run `actuated-cli auth` first, so that you can get a Personal Access Token with the appropriate scopes from GitHub.
 
diff --git a/docs/tasks/debug-ssh.md b/docs/tasks/debug-ssh.md
@@ -43,7 +43,7 @@ Next, trigger a build via the workflow_dispatch event or a git push to the maste
 
 Open `https://$SSH_GATEWAY/list` in your browser and look for your session, you can log in using the SSH command outputted for you.
 
-Alternatively, you can view your own SSH sessions from the [actuated dashboard](https://dashboard.actuated.dev).
+Alternatively, you can view your own SSH sessions from the [actuated dashboard](https://dashboard.actuated.com).
 
 Whenever you have a build that you just can't figure out - or if you want to explore the runner and tune it up to your needs, then you can simply add `- uses: self-actuated/connect-ssh@master` where you want to pause the build.
 
diff --git a/docs/tasks/local-github-cache.md b/docs/tasks/local-github-cache.md
@@ -227,5 +227,5 @@ jobs:
 
 ## Further reading
 
-* From our blog: [Fixing the cache latency for self-hosted GitHub Actions](https://actuated.dev/blog/faster-self-hosted-cache)
+* From our blog: [Fixing the cache latency for self-hosted GitHub Actions](https://actuated.com/blog/faster-self-hosted-cache)
 * A primer on using the GitHub Actions cache: [Using caching in builds](/examples/github-actions-cache/)
diff --git a/docs/test-build.md b/docs/test-build.md
@@ -92,7 +92,7 @@ Note that if you're running on an Arm server, You'll adapt the prefix of `runs-o
 
 2. Hit commit, and watch the VM boot up.
 
-    You'll be able to see the runners registered for your organisation on the [Actuated Dashboard](https://dashboard.actuated.dev) along with the build queue and stats for the current day's builds.
+    You'll be able to see the runners registered for your organisation on the [Actuated Dashboard](https://dashboard.actuated.com) along with the build queue and stats for the current day's builds.
 
 3. If you're curious
 
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
@@ -20,7 +20,7 @@ If you'd like to upgrade your plan for more concurrent builds, a higher level of
 
 ## The Actuated Dashboard
 
-The first port of call should be the [Actuated Dashboard](https://dashboard.actuated.dev) where you can check the status of your agents and see the current queue of jobs.
+The first port of call should be the [Actuated Dashboard](https://dashboard.actuated.com) where you can check the status of your agents and see the current queue of jobs.
 
 For security reasons, an administrator for your GitHub Organisation will need to approve the Actuated Dashboard for access to your organisation before team members will be able to see any data. Send them the link for the dashboard, and have them specifically tick the checkbox for your organisation when logging in for the first time.
 
@@ -90,7 +90,7 @@ Bear in mind that if you set the RAM higher than the default, this may result in
 
 The maximum amount of vCPU that can be set for a single job is 32 vCPU, this is an implementation detail of Firecracker and may change in the future.
 
-To find out exactly how many resources are required, see our [blog post on right sizing with the vmmeter tool](https://actuated.dev/blog/right-sizing-vms-github-actions).
+To find out exactly how many resources are required, see our [blog post on right sizing with the vmmeter tool](https://actuated.com/blog/right-sizing-vms-github-actions).
 
 ## Disk space is running out for a job
 
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -1,7 +1,7 @@
 site_name: Actuated
 site_description: Realise the potential of blazingly fast builds.
 site_author: OpenFaaS Ltd
-site_url: https://docs.actuated.dev/
+site_url: https://docs.actuated.com/
 
 # Repository
 repo_name: self-actuated/actuated

Original file line number	Diff line number	Diff line change
`@@ -94,4 +94,4 @@ The full example is available on [GitHub](https://github.com/skatolo/nested-fire`
`94`	`94`
`95`	`95`	`For more examples and use-cases see:`
`96`	`96`
`97`		`-- [How to run a KVM guest in your GitHub Actions](https://actuated.dev/blog/kvm-in-github-actions)`
	`97`	`+- [How to run a KVM guest in your GitHub Actions](https://actuated.com/blog/kvm-in-github-actions)`