Document the Supabase stack - #96
Draft
csandanov wants to merge 2 commits into
Draft
Conversation
Describe configuration, persistent credentials, coordinated recovery and initial feature limits. Document fixed component image tags for service bundles.
Document the released database image, fresh-volume imports and the matching tokens and object backups required for coordinated recovery.
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
1 participant
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.
Add a Supabase guide covering setup, database linkage, SMTP, optional S3 storage, persistent credentials, coordinated recovery and initial feature limits. Add navigation and explain fixed per-component image tags for bundled services.
Describe the released
wodby/supabase-postgresimage and native database import into a fresh volume. Explain target database passwords, retained signing/encryption tokens and the matching filesystem or S3 objects needed before resuming writers.Validation: the Wodby 2 documentation builds with
mkdocs build --strictthrough Wodby CLI. Local acceptance verifies real Auth/REST/Realtime APIs, Studio authentication, RLS, pause/resume, upgrades, Vault decryption and coordinated native database/filesystem/S3 recovery.Supabase stack 0.1.0 and both service releases are published. Keep this guide in draft until the catalog entry is merged and the stack is available in the platform. Local tests validate image/chart behavior; no platform deployment or import was performed.
Related changes: Supabase stack, PostgreSQL service.