2.2 KiB
2.2 KiB
Sojorn Migration Runbook: Supabase to Golang VPS
This document outlines the step-by-step process for cutover from Supabase to the self-hosted Golang engine.
Phase 1: Infrastructure Setup
- Provision VPS: Ubuntu 22.04 LTS recommended (2 vCPU, 4GB RAM minimum).
- Install Dependencies:
sudo apt update && sudo apt install -y postgresql postgis nginx certbot python3-certbot-nginx - Configure Database:
- Create
sojorndatabase. - Enable extensions:
uuid-ossp,pg_trgm,postgis.
- Create
Phase 2: Data Migration
- Export from Supabase:
- Use
pg_dumpto export schema and data from your Supabase project. - Alternatively, use the Supabase CSV export for specific tables if the schema changes significantly.
- Use
- Import to VPS:
psql -h localhost -U youruser -d sojorn -f supabase_dump.sql - Run Go Migrations:
- The Go backend uses
golang-migrate. Ensure the version table is synced if you are not starting from scratch.
make migrate-up - The Go backend uses
Phase 3: Deployment
- Clone & Build:
git clone <your-repo> /opt/sojorn cd /opt/sojorn/go-backend go build -o bin/api ./cmd/api/main.go - Configure Nginx:
- Set up reverse proxy to port 8080.
- Configure SSL with Certbot.
- Start Systemd Service:
sudo ./scripts/deploy.sh
Phase 4: Cutover (Zero Downtime Strategy)
- Parallel Run: Keep both Supabase and Go VPS running.
- DNS Update: Point your API subdomain (e.g.,
api.sojorn.net) to the new VPS IP. - TTL Check: Ensure DNS TTL is low (e.g., 300s) before starting.
- Monitor: Watch logs for 4xx/5xx errors.
journalctl -u sojorn-api -f
Phase 5: Decommission Supabase
- Once traffic has fully shifted and no errors are reported, you can disable Supabase Edge Functions.
- Keep the Supabase project active for a week as a backup database if needed.
Rollback Plan
- If critical issues occur on the VPS, point the DNS back to the Supabase Edge Functions URL.
- Restore any data written to the VPS back to Supabase if necessary (Dual-write during transition is recommended if possible).