generated from bisco/codex-bootstrap
feat: add wordpress site variant
This commit is contained in:
+21
-10
@@ -1,19 +1,30 @@
|
||||
# Runbook
|
||||
|
||||
Operational runbook for this project.
|
||||
## Installation screen remains visible
|
||||
|
||||
## Common tasks
|
||||
1. Check `docker compose ps` for healthy database and WordPress services.
|
||||
2. Run `docker compose --profile tools run --rm wp-cli /scripts/bootstrap.sh`.
|
||||
3. Inspect `docker compose logs wordpress db` without printing secret values.
|
||||
|
||||
Document routine operational tasks here.
|
||||
## NGINX returns 502
|
||||
|
||||
## Troubleshooting
|
||||
1. Run `docker compose ps` and `docker compose exec proxy nginx -t`.
|
||||
2. Check the WordPress health status and `docker compose logs proxy wordpress`.
|
||||
3. Confirm the request host is exactly `azionelab.org`; unknown hosts return 404.
|
||||
|
||||
Document known issues, symptoms, checks, and remediation steps.
|
||||
## Images or theme are missing
|
||||
|
||||
1. Confirm `wordpress_data` is mounted in both WordPress and WP-CLI.
|
||||
2. Run `docker compose --profile tools run --rm wp-cli -c 'wp theme status azionelab'`.
|
||||
3. Verify file ownership before changing permissions; never make the tree world-writable.
|
||||
|
||||
## Certificate issuance fails
|
||||
|
||||
Verify public DNS, inbound port 80, the operator email, and staging mode. Request a
|
||||
missing `/.well-known/acme-challenge/` path: an NGINX 404 confirms the route is yours.
|
||||
Avoid repeated production-CA retries while debugging.
|
||||
|
||||
## Rollback
|
||||
|
||||
Document rollback procedures here.
|
||||
|
||||
## Emergency contacts
|
||||
|
||||
Document project-specific escalation paths if appropriate.
|
||||
Revert the deployment commit and rebuild while preserving all named volumes. Restore
|
||||
database/files only for a data rollback and only from a verified coordinated backup.
|
||||
|
||||
Reference in New Issue
Block a user