docs(site): Show how to store the deploy token, and use the org npm scope - #20
Merged
Merged
Conversation
GitHub Packages only accepts the @LasVegasForTransit scope, and every other workspace dependency here already uses it. Rename apps/site's own package from @lvbt/lvwwd-site to @lasvegasfortransit/site, matching the name the template repositories use for their own apps/site package. No other file referenced the old name; pnpm check and a full build pass under the new one. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The deploy token section only told a maintainer to paste the token into pnpm bootstrap --production, with no direct way to store it. The Deploy workflow needs CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID in the production GitHub environment before it can publish lvwwd.org, so add the exact commands to set both without running the full bootstrap tool: gh secret set CLOUDFLARE_API_TOKEN --env production (value from standard input) and gh secret set CLOUDFLARE_ACCOUNT_ID --env production with the account ID shown in the guide, since it is not a secret value. Co-Authored-By: Claude Sonnet 5 <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
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.
TL;DR
The production setup guide now shows how to store the Cloudflare deploy token and account ID with
gh secret set, and the site package uses the org's npm scope.Changes
The production deploy fails today because the GitHub
productionenvironment has noCLOUDFLARE_API_TOKEN. The setup guide explained how to create the account-owned token but not how to store it, so it now gives the exactgh secret set CLOUDFLARE_API_TOKEN --env productionandCLOUDFLARE_ACCOUNT_IDcommands.apps/sitewas still named@lvbt/lvwwd-site. GitHub Packages only accepts the owning organization's scope, so the org standard is@lasvegasfortransit/*; the package is now@lasvegasfortransit/site, matching the template repositories. Nothing else referenced the old name.pnpm check(296 tests) andpnpm buildpass.Follow-ups and Next Work
A maintainer still has to create the token and run the documented commands.
🤖 Generated with Claude Code