Files

1.2 KiB

Rollback Plan - ASF test host

What went wrong Rollback
Bad release (health check red or wrong behaviour) On the Pi: ln -sfn releases/<previous> current && systemctl --user restart andreaslopfotografie-test. The previous release is always kept (prune keeps current + 1).
Proxy route broke the test site Restore the saved nginx server block on the proxy Pi (manual step 10), test config, reload; the old nginx fallback on the app Pi serves the site again.
Pipeline misbehaves Set ASF_TEST_DEPLOY_ENABLED to anything but true: all ASF jobs are skipped, SlpSoftware is unaffected.
Shared Core change misbehaves on another host Redeploy the previous release of that host the same way. The new behaviour is opt-in (forwarded headers) or equivalent to before (limiter buckets share the proxy address when no proxy is configured).
Database Migrations run automatically at start and are forward-only. The test database is backed up by the Pi DB backup (step 7); restore from that backup if a migration must be undone.
Setup token leaked Replace Identity__Setup__Token in shared/env and restart, or remove it once the first administrator exists.