Repository navigation
Prepare isolated CFH signup in shared Supabase - #2
Draft
clearframeworks wants to merge 1 commit into
Draft
clearframeworks wants to merge 1 commit into
clearframeworks wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
CFH signup needs a database connection. Prepare it for the owner's selected existing
retehost-cfwproject, with application data incfh, privileged helpers incfh_private, and a CFH-specific auth cookie. Auth identities and project capacity remain shared.The generated migration scopes the three reviewed foundation migrations to CFH and preserves existing public/private application tables and grants. Signup metadata identifies CFH for email routing only, never authorization.
Deployment is blocked: the shared database reports read-only mode and 1566 MB of data. Supabase rejected the migration before applying changes. No CFH schemas or production environment variables were created. Signup is not live. The activation guide records the remaining capacity, callback, email delivery, API exposure, and hosted signup verification steps. Do not merge for activation until those are resolved.
Validation: 40 unit/database tests, 28 browser tests, TypeScript check, production build, tracked-source credential scan, and staged whitespace check passed. Database tests verify existing-app preservation, anonymous access boundaries, cross-user profile isolation, and privileged role protection. Hosted email and signup acceptance remain pending.