patrick/sojorn
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
sojorn/sojorn_docs/legacy/MIGRATION_PLAN.md
Patrick Britton 38653f5854 Sojorn Backend Finalization & Cleanup - Complete Migration from Supabase 
##  Phase 1: Critical Feature Completion (Beacon Voting)
- Add VouchBeacon, ReportBeacon, RemoveBeaconVote methods to PostRepository
- Implement beacon voting HTTP handlers with confidence score calculations
- Register new beacon routes: /beacons/:id/vouch, /beacons/:id/report, /beacons/:id/vouch (DELETE)
- Auto-flag beacons at 5+ reports, confidence scoring (0.5 base + 0.1 per vouch)

##  Phase 2: Feed Logic & Post Distribution Integrity
- Verify unified feed logic supports all content types (Standard, Quips, Beacons)
- Ensure proper distribution: Profile Feed + Main/Home Feed for followers
- Beacon Map integration for location-based content
- Video content filtering for Quips feed

##  Phase 3: The Notification System
- Create comprehensive NotificationService with FCM integration
- Add CreateNotification method to NotificationRepository
- Implement smart deep linking: beacon_map, quip_feed, main_feed
- Trigger notifications for beacon interactions and cross-post comments
- Push notification logic with proper content type detection

##  Phase 4: The Great Supabase Purge
- Delete function_proxy.go and remove /functions/:name route
- Remove SupabaseURL, SupabaseKey from config.go
- Remove SupabaseID field from User model
- Clean all Supabase imports and dependencies
- Sanitize codebase of legacy Supabase references

##  Phase 5: Flutter Frontend Integration
- Implement vouchBeacon(), reportBeacon(), removeBeaconVote() in ApiService
- Replace TODO delay in video_comments_sheet.dart with actual publishComment call
- Fix compilation errors (named parameters, orphaned child properties)
- Complete frontend integration with Go API endpoints

##  Additional Improvements
- Fix compilation errors in threaded_comment_widget.dart (orphaned child property)
- Update video_comments_sheet.dart to use proper named parameters
- Comprehensive error handling and validation
- Production-ready notification system with deep linking

##  Migration Status: 100% Complete
- Backend: Fully migrated from Supabase to custom Go/Gin API
- Frontend: Integrated with new Go endpoints
- Notifications: Complete FCM integration with smart routing
- Database: Clean of all Supabase dependencies
- Features: All functionality preserved and enhanced

Ready for VPS deployment and production testing!
2026-01-30 09:24:31 -06:00

2.1 KiB
Raw Blame History

Migration Plan: Supabase to Golang VPS

1. Project Overview

  • Source: Supabase (Edge Functions, PostgreSQL with RLS, Auth, Storage)
  • Target: Golang (Gin/Echo), Self-hosted PostgreSQL, Nginx, Systemd
  • App: Sojorn (Social Media platform with Beacons/Location features)

2. Infrastructure Setup (VPS)

  • OS: Ubuntu 22.04 LTS
  • DB: PostgreSQL 15+ with PostGIS, pg_trgm, uuid-ossp
  • Proxy: Nginx (SSL via Certbot)
  • Process Manager: Systemd

3. Database Migration

  • Export schema from Supabase.
  • Convert RLS policies to application logic (Go middleware/services).
  • Migrate Auth users to a local users table (integrating with profiles).
  • Set up Go migration tool (golang-migrate).
  • Data migration strategy: Dump and restore, or script-based sync.

4. Auth System

  • Implement JWT validation (compatible with Supabase or new secret).
  • Login/Signup handlers porting.
  • Middleware for auth.uid() equivalent.

5. API Mapping (Functions to Handlers)

Supabase Function Go Endpoint Status
signup POST /api/v1/auth/signup Pending
profile GET /api/v1/profiles/:id Pending
feed-sojorn GET /api/v1/feed Pending
publish-post POST /api/v1/posts Pending
create-beacon POST /api/v1/beacons Pending
search GET /api/v1/search Pending
... and more ...

6. Implementation Phases

Phase 1: Preparation

  • Initial Audit
  • VPS Configuration
  • Repository Setup (Go scaffolding)

Phase 2: Core Engine

  • Database connection & migrations
  • Auth & Middleware
  • Shared models & utils

Phase 3: Feature Porting

  • User & Profile management
  • Posting & Feed logic
  • Beacon (GIS) system
  • Notifications (FCM integration)
  • E2EE Chat (Session Manager)

Phase 4: Finalization

  • Unit & Integration Tests
  • Deployment Scripts
  • Cutover Plan

7. To-Be-Decided (TBD)

  • Request volume and growth expectations.
  • VPS specifications.
  • Monitoring preferences (Prometheus/Grafana).
  • Storage strategy (Local vs S3/R2).