From 0a59583f510cde2bbae594ba44b9584b4e905b1e Mon Sep 17 00:00:00 2001 From: mkrause612 Date: Thu, 12 Feb 2026 08:36:20 -0600 Subject: [PATCH] [ARCHIVE] Removed docs/planning/migration-rollback.md (moved to docs/archive/planning/migration-rollback.md) --- docs/planning/migration-rollback.md | 76 ----------------------------- 1 file changed, 76 deletions(-) delete mode 100644 docs/planning/migration-rollback.md diff --git a/docs/planning/migration-rollback.md b/docs/planning/migration-rollback.md deleted file mode 100644 index 0a359bb..0000000 --- a/docs/planning/migration-rollback.md +++ /dev/null @@ -1,76 +0,0 @@ -# Migration Rollback Plan - -## If Things Go Wrong - -### Immediate Rollback (During Migration) - -**If service fails on new VPS:** -1. DO NOT stop TX1 service -2. Revert DNS in Cloudflare (instant) -3. TX1 service continues working -4. Debug VPS issue offline - -**Maximum Downtime:** DNS TTL (5 minutes) - ---- - -## Service-Specific Rollback - -### Gitea Rollback -```bash -# On Cloudflare -git.firefrostgaming.com A record → 38.68.14.26 (TX1) - -# On TX1 -systemctl start gitea -``` - -### Uptime Kuma Rollback -```bash -# On Cloudflare -status.firefrostgaming.com A record → 38.68.14.26 (TX1) - -# On TX1 -systemctl start uptime-kuma -``` - -### MkDocs Rollback -```bash -# On Cloudflare -docs.firefrostgaming.com A record → 38.68.14.26 (TX1) - -# On TX1 -systemctl start mkdocs -``` - ---- - -## Data Recovery - -### If Backup Needed -All backups stored in `/root/migration-backups/` on TX1: -- `gitea-backup.tar.gz` + `gitea-dump.sql` -- `kuma-backup.tar.gz` -- `mkdocs-source.tar.gz` - -**Retention:** 7 days after successful migration - ---- - -## Lessons Learned Log - -**What went wrong:** -- - -**Root cause:** -- - -**How we fixed it:** -- - -**How to prevent next time:** -- - ---- - -**Remember:** Don't panic. TX1 services are still running. DNS changes are instant.