toph/ci-actions
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

docs: cold-start note for maintainer, simplify infra requirements

Browse source
This commit is contained in:
Christopher Mühl 2026-02-18 13:21:23 +01:00
parent af9a4e3e29
commit ada83e01b5
No known key found for this signature in database
GPG key ID: 925AC7D69955293F
1 changed files with 8 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
deploy-static-site/README.md
View file

@ -38,10 +38,17 @@ Builds a Nix flake site, uploads a tarball to S3, and deploys it via Nomad using
## Infrastructure Requirements ## Infrastructure Requirements
- `registry.toph.so/static-server:latest` must be pushed (see `images/flake.nix` and the `build-static-server` workflow)
- S3 bucket (`nix-cache` by default) must exist and be writable with the supplied credentials - S3 bucket (`nix-cache` by default) must exist and be writable with the supplied credentials
- Nomad namespace `static-sites` is created automatically on first deploy - Nomad namespace `static-sites` is created automatically on first deploy
## Cold-Start (maintainer note)
The `static-server` image (`registry.toph.so/static-server:latest`) is built and pushed by
the `build-static-server` workflow in this repo. It runs automatically when `deploy-static-site/images/flake.nix`
changes, or can be triggered manually via `workflow_dispatch`.
On a fresh infrastructure setup, run that workflow once before deploying any site.
## Site Flake Requirements ## Site Flake Requirements
The site repo's flake must expose a package output that produces a directory of static files: The site repo's flake must expose a package output that produces a directory of static files: