Repository navigation
Docs: make the Railway steps require FOUNDER_OS_ACCESS_TOKEN - #16
Open
Bennettxai wants to merge 1 commit into
Open
Bennettxai wants to merge 1 commit into
Bennettxai wants to merge 1 commit into
Conversation
The access gate shipped in #1 / f30a715, but the README section that documented it was lost in a later rewrite: the token appeared nowhere in README.md or .env.example, and the Railway steps still walked a first-time deployer onto a public URL with every route open (issue #2). - Railway steps now set the token before any credentials, and end with a check that the deployed URL shows the challenge page - New "Access control" section: no built-in auth, unset means open, how to generate and enter the token - .env.example lists FOUNDER_OS_ACCESS_TOKEN first - tests/access-gate.test.ts pins all three so the docs can't drift again Gate behaviour is unchanged (still opt-in, so local dev and the read-only demo stay open). Closes #2 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Closes #2.
Why
The access gate itself shipped in #1 and
f30a715, and it works. But the README section that documented it was lost in a later rewrite. OnmaintodayFOUNDER_OS_ACCESS_TOKENappears nowhere inREADME.mdor.env.example, and Deploying to Railway still walks a first-time deployer onto a public*.up.railway.appURL with every page and API route open. That is the exact gap #2 reported.What changed
.env.examplelistsFOUNDER_OS_ACCESS_TOKENfirst, marked required for public deployments.tests/access-gate.test.tspins all three, so the docs cannot silently drift away from the gate again.Gate behaviour is unchanged. It stays opt-in, so local dev and the read-only demo deployment remain open with no setup.
Verification
Run under Node 22 (the version
enginespins):vitest run: 280 files, 3145 tests passedtsc --noEmit: cleanThe three new tests were written first and failed against
mainbefore the docs change.🤖 Generated with Claude Code