Repository navigation
Conversation
|
Starting deployment of preview ⏳... |
This branch has not been 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
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.
Why
Companion to revisit-studies/study#1508. The 3.0 Supabase instructions still tell users to start the bundled Compose stack that the application PR removes.
Architecture
Update the two unversioned Supabase pages to describe the separate, pinned upstream deployment and reVISit's integration files. Link setup, migration, rollback, and ongoing operations to the reviewed application commit; all detailed migration commands remain in the application repository's
supabase/directory. Permanent commit links work before #1508 merges and survive deletion of its branch.The website explains fresh-only initialization, deployment secrets versus public application settings, anonymous participant sessions, persistent storage, and coordinated backups. Authentication now uses
GITHUB_OAUTH_SECRETand explicitly enables the GitHub Compose override. Typedoc is assumed to remain generated by the existing release pipeline.User-facing impact
New installations follow the supported upstream setup. Existing MinIO/pgsty users get prominent migration and rollback links. Study Designers get matching GitHub authentication instructions.
Validation
yarn typecheckpassed.yarn buildpassed, with an optional Vegacanvasdependency warning.git diff --checkpassed.Risk and rollout
Keep this draft until application PR #1508 lands so the matching support files are available in the normal application checkout. The linked procedures are pinned to application commit
1669a47fa63860b39723b4e92a10f73dbbb8936c; update the links deliberately when adopting a newer procedure. This changes documentation only and targets3.0.