When we migrated to Azure Container Apps (#1029) I forgot that the documentation was hosted via mkdocs serve and a special route in the Caddyfile. There was nothing in the new setup that reproduced this, so we fell back to the old iframe docs route which referenced a static site that no longer exists.
To put the docs back to how they were I've configured Whitenoise to serve them. Unfortunately this means we need to run docker compose build twice because we use the Django container to run mkdocs as we have plugins installed. In practice though all the base layers are already built so it's not much slower.
I've tested this by manually editing the GitHub deploy workflow to deploy to staging from this branch.
When we migrated to Azure Container Apps (#1029) I forgot that the documentation was hosted via
mkdocs serve
and a special route in the Caddyfile. There was nothing in the new setup that reproduced this, so we fell back to the old iframe docs route which referenced a static site that no longer exists.To put the docs back to how they were I've configured Whitenoise to serve them. Unfortunately this means we need to run
docker compose build
twice because we use the Django container to run mkdocs as we have plugins installed. In practice though all the base layers are already built so it's not much slower.I've tested this by manually editing the GitHub deploy workflow to deploy to staging from this branch.