feat: build headless theatre laboratory website

docs/operations.md

@@ -1,13 +1,44 @@
 # Operations
 
-Describe operational procedures.
+## Routine commands
 
-Include:
+```bash
+docker compose up --build -d
+docker compose ps
+docker compose logs -f backend frontend postgres
+docker compose down
+```
 
-- startup and shutdown;
-- health checks;
-- logs;
-- monitoring;
-- backup and restore;
-- routine maintenance;
-- known operational risks.
+Compose health checks PostgreSQL and Django. The public health endpoint is
+`http://localhost:8000/health/`; the aggregate content endpoint is
+`http://localhost:8000/api/site/home/`.
+
+Apply schema changes with `docker compose exec backend python manage.py migrate`.
+Create editors with `createsuperuser`; use Wagtail permissions for later non-superuser
+accounts.
+
+The backend applies migrations at container startup. To permanently reset local
+state, use `docker compose down --volumes`; this deletes both database and media.
+
+## Backup and restore
+
+Back up the database and media at the same logical point in time:
+
+```bash
+mkdir -p backups/media
+docker compose stop frontend backend
+docker compose exec -T postgres sh -c 'pg_dump -U "$POSTGRES_USER" "$POSTGRES_DB"' > backups/database.sql
+docker compose cp backend:/app/media/. backups/media/
+docker compose start backend frontend
+```
+
+Restore is destructive: verify the backup in a disposable environment and take a fresh
+backup first. Then stop both applications, recreate and restore the database, replace
+the media content, restart, and verify health, API, admin login, and several images.
+Keep real backups encrypted and off-host with a defined retention policy.
+
+## Known risks
+
+- Frontend fallback content can mask a CMS outage, so monitor backend health directly.
+- Local named volumes are not off-host backups.
+- Development media serving is unsuitable for production traffic.