Skip to content

Auto Deploy

To streamline the merging and deployment process, this wiki automatically deploys upon merge to master.

In future, we're hoping to add preview environments for each PR.

Note: This process isn't live, yet.

How does it work?

Here's how the autodeploy works:

1. PR is merged

After a successful code review, the PR is merged. On merge, a GitHub Actions workflow starts.

2. Build Site

The workflow builds the exact same container as in local development, so the output build is exactly the same. Unlike local development, this doesn't spin up a development server, instead it saves the site to the filesystem.

3. Build Production Container

The development server which comes with mkdocs isn't suited, nor suitable, for a production environment. For this, we build a custom container based off NGINX, which is far better suited, and allows for more control over the server.

4. Publish Container

Once the production container is built, it's pushed to GitHub's container registry.

5. Server Pull

Every 30 seconds, the server polls GitHub's container registry for new containers, using watchtower. When a new container is pulled, it's

6. Restart

Once the new container is pulled, watchtower stops the running container, and replaces it with the new one. This is done automatically as quickly as possible, to minimise potential downtime during the switchover.


The configuration for all this is available on GitHub.

Some notable files: