Manage routine operations through Ansible
This commit is contained in:
@@ -50,4 +50,13 @@ Official stance: prefer environment variables; `config.json` is **not** the reco
|
||||
5. Do not commit secrets; do not copy passwords from Obsidian into this repo.
|
||||
6. Verify SMTP with AUTH (not TCP-only) — [vaultwarden-health](../runbooks/vaultwarden-health.md) §5.
|
||||
|
||||
## Operations path
|
||||
|
||||
Use `ansible/playbooks/health-report.yml --limit vaultwarden` for routine
|
||||
status. After a reviewed effective-configuration change that needs a container
|
||||
recreate, use the allowlisted `compose-reconcile.yml` target `vaultwarden`.
|
||||
Add `service_reconcile_restart_traefik=true` only when the documented
|
||||
post-recreate 404 occurs. Direct Compose commands remain diagnostic tools, not
|
||||
the routine control path.
|
||||
|
||||
Replay migration steps: [runbooks/vaultwarden-sqlite-to-postgres.md](../runbooks/vaultwarden-sqlite-to-postgres.md).
|
||||
|
||||
Reference in New Issue
Block a user