feat: Implement Supabase migration #2461
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add @supabase/supabase-js dependency - Create Supabase service for auth and database operations - Implement Supabase authenticator to replace Cognito - Create Supabase data source to replace JSON:API remote - Update login/register components to use Supabase auth - Configure CSP for Supabase domains - Add environment configuration for Supabase - Preserve existing Orbit.js data flow and strategies This migration maintains the existing data architecture while replacing AWS Cognito + API Gateway with Supabase for simplified maintenance.
- Add recent changes section documenting Supabase migration - Highlight key benefits of the migration - Document preserved architecture and new capabilities
Contributor
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
- Remove ember-cognito dependency from package.json - Convert Supabase authenticator from .js to .ts with proper types - Remove unused Cognito service and authenticator files - Remove backup file (remote.js.backup) - Update CSP to remove AWS Cognito domains - Clean up environment config removing legacy Cognito settings - All builds passing successfully This completes the cleanup phase of Supabase migration.
- Remove package-lock.json (npm lock file) - Remove node_modules directory - Prepare for proper pnpm setup - Will resolve pnpm installation issues separately Maintains clean state for package manager migration.
- Add complete Supabase database schema with RLS policies - Add migration helper functions for AWS → Supabase data transfer - Add sample data creation for new users - Create detailed migration guide for users - Fix SUPABASE_ANON_KEY typo in environment config - Add palettes_with_colors view for efficient queries - Include proper constraints, indexes, and triggers - Support data transformation from Orbit.js format - Add row-level security for user isolation This provides all SQL and documentation needed for seamless user migration from AWS Cognito + DynamoDB to Supabase.
- Resolved all merge conflicts between main and feature branch - Kept Supabase migration infrastructure (authenticator, service, remote source) - Preserved our environment configuration with SUPABASE_ANON_KEY fix - Maintained comprehensive migration documentation and schema - Accepted main branch improvements while protecting our changes Ready for PR on original feature branch.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.