v0.6.0 — Operations
Sixth release of the infra repository: Operations - backup, restore, update, cleanup, and manual deploy tooling.
Added
scripts/backup.sh- local, verified, rotated backups per host role (pg_dump -Fcfor Postgres, volume tars forjenkins_home/portainer_data/registry_data); off-host replication is documented (docs/backup.md), not scripted, since the destination varies per deploymentscripts/restore.sh- destructive, so it's a dry run unless--yes-i-am-sureis passed; validates Postgres connectivity and table presence after a restorescripts/update.sh- on-demandapt upgrade+docker compose pull/upper role, image prune, idempotent logrotate config installscripts/cleanup.sh- periodicdocker system prune/build-cache prune, never touches volumesscripts/deploy.sh- manual/fallback counterpart tovars/standardDeployPipeline.groovy's SSH deploy stage (pull infra config -> tag rollback images -> pull -> up -> wait-for-healthy -> roll back on failure), for when Jenkins isn't the one triggering deploymentscripts/logrotate/infra-nginx.conffor the file-based nginx logs added in v0.5.0- Real content for
docs/backup.mdanddocs/restore.md(stubs since v0.1.0), including a disaster-recovery walkthrough
Fixed
- Two internal-consistency gaps caught while writing this phase:
docs/roadmap.mdstill showed v0.5.0 as "In Progress" after it had already shipped;docs/project-specification.md's Operations section was missingrestore.sh/cleanup.sh
Notes
- None of these scripts have been run against a live host yet -
restore.shanddeploy.shboth have their own built-in safety gates for that first real run (explicit confirmation flag, automatic image rollback on failed healthcheck respectively)
What's next
v0.7.0 - Observability (Uptime Kuma, Prometheus, Grafana, Node Exporter, cAdvisor, alerting, monitoring dashboards).
Full changelog: CHANGELOG.md