docs(fumadocs): document NOTRA_API_KEY turbo passthrough and empty-blog troubleshooting#118
Draft
tembo[bot] wants to merge 1 commit into
Draft
docs(fumadocs): document NOTRA_API_KEY turbo passthrough and empty-blog troubleshooting#118tembo[bot] wants to merge 1 commit into
tembo[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Requesting review from @leoisadev1 who has experience with the following files modified in this PR:
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Follow-up documentation for the Notra-powered blog build pipeline, triggered by the merge of #116. That PR fixed a production incident — the live blog rendered empty because turbo's strict env mode stripped
NOTRA_API_KEYfrom the fumadocs build (the Vercel env var never reachedscripts/fetch-notra-posts.ts). The fix lived only inturbo.json; the operational knowledge behind it was undocumented, so this captures it where developers already look.All changes are to the existing
apps/fumadocs/README.md"Blog content (Notra)" section — no new pages — and every statement is verified against source.Docs added/updated
apps/fumadocs/README.mdpassThroughEnvinapps/fumadocs/turbo.json, because turbo's strict env mode strips undeclared variables. Also noted that Bun auto-loads.env.locallocally (which is why local builds masked the bug).[notra] NOTRA_API_KEY is not setlog line, the two-point checklist (Vercel env var +passThroughEnv), and the success log to confirm a good build.blog-schedule.yml's cron (30 13 * * *, its own comment: "Daily safety net") runs daily.Codepaths covered
apps/fumadocs/turbo.json—passThroughEnv: ["NOTRA_API_KEY"](added in fix(docs): pass NOTRA_API_KEY through turbo so the blog builds with posts #116)apps/fumadocs/scripts/fetch-notra-posts.ts— the skip-and-keep-snapshot behavior and the exact warning/success log linesapps/fumadocs/package.json—buildruns the fetch beforevite build.github/workflows/blog-schedule.yml— the daily rebuild cronKey knowledge gaps addressed
passThroughEnvrequirement, previously implicit and the root cause of the fix(docs): pass NOTRA_API_KEY through turbo so the blog builds with posts #116 incident..env.localloading bypasses turbo's env filtering, so the gap only surfaces in CI/Vercel.Documentation-only change; no SDK/CLI behavior touched, so no changeset.
Triggered by the merge of #116 (
fix(docs): pass NOTRA_API_KEY through turbo to the docs build).