Dev workspace setup: SETUP.md + token-less local build (PRO-14)#29
Open
huntsyea wants to merge 2 commits into
Open
Dev workspace setup: SETUP.md + token-less local build (PRO-14)#29huntsyea wants to merge 2 commits into
huntsyea wants to merge 2 commits into
Conversation
Stand up the contributor onboarding for the dev workspace (PRO-14): - Add SETUP.md: verified prerequisites (Node >=20.9, pnpm), install, env var sourcing (Basehub token/webhook secret), commands, graceful- degradation behavior, the add-a-virtue workflow, and Vercel link notes. - Add `build:local` script (`next build`) so the app builds without a BASEHUB_TOKEN using the committed basehub-types.d.ts. The default `basehub && next build` still hard-fails token-less at the codegen step; documented in SETUP.md. - Drop NODE_ENV from .env.example (Next.js manages it and warns when set manually) and document Basehub token sourcing inline. - README: point to SETUP.md and correct stale Node 18 / prerequisites. Co-Authored-By: Paperclip <noreply@paperclip.ing>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The dudesdesign/classical-virtues Vercel project already holds BASEHUB_TOKEN, BASEHUB_WEBHOOK_SECRET, and BLOB_READ_WRITE_TOKEN. Document linking + env pull as the fastest way to populate a git-ignored .env.local, verified to make the full `basehub && next build` succeed and live stories render. Co-Authored-By: Paperclip <noreply@paperclip.ing>
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
2 participants
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.
Summary
Stands up
classical-virtuesas a working dev workspace and documents onboarding (PRO-14). No secrets are committed.Verification (all run locally)
pnpm installpnpm run lintpnpm run build:local(next build)pnpm run build(basehub && next build)basehubcodegen step (🔴 Token not found) — expected; succeeds whereBASEHUB_TOKENis set (CI/Vercel)pnpm run devnext devboots;/,/stories,/about→ 200,/api/stories→[](graceful degradation).basehub devlogs a token warning but is backgrounded and non-blockingChanges
SETUP.md(new) — concise verified quickstart: prerequisites, install, env-var sourcing, commands, graceful degradation, add-a-virtue workflow, Vercel link notes.package.json— addbuild:local(next build) so the app builds without aBASEHUB_TOKENusing the committedbasehub-types.d.ts..env.example— dropNODE_ENV(Next.js manages it and warns when set manually); document Basehub token/secret sourcing inline.README.md— point toSETUP.md; correct stale Node 18 prerequisite.Notes for reviewers
buildscript intentionally keepsbasehub && next build(matches the Vercel build command).build:localis the token-less escape hatch..vercel/dir exists).🤖 Generated with Claude Code
Co-Authored-By: Paperclip noreply@paperclip.ing