docs: clarify Railway persistence setup - #5607
Open
clockwork-labs-bot wants to merge 1 commit into
Open
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
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.
Description of Changes
Fixes #5587.
Clarifies that Railway deployments must keep the SpacetimeDB server data directory inside the mounted Railway volume, using
/stdb/dataunder the template's/stdbvolume. Also adds a short service-configuration checklist that calls out--data-dir=/stdb/dataandRAILWAY_RUN_UID=0for Railway volume permission failures.API and ABI breaking changes
None. Documentation only.
Expected complexity level and risk
Testing
git diff --checkpnpm --dir docs build