Skip to content

[codex] Move docs-site Render blueprint into docs-site#596

Merged
cssbruno merged 1 commit into
mainfrom
codex/docs-site-render-build
Jun 20, 2026
Merged

[codex] Move docs-site Render blueprint into docs-site#596
cssbruno merged 1 commit into
mainfrom
codex/docs-site-render-build

Conversation

@cssbruno

@cssbruno cssbruno commented Jun 20, 2026

Copy link
Copy Markdown
Owner

Summary

  • Move the Render Blueprint from the repository root to docs-site/render.yaml.
  • Configure the service with rootDir: docs-site, an inline Build Command that generates dist/site before go build, and startCommand: ./app.
  • Update docs-site deployment notes for the Render UI settings.

Why

The default Render Go service command can run go build -tags netgo -ldflags '-s -w' -o app from the wrong directory. From the repo root, that builds the root library package into a non-executable app archive, which then fails at start with ./app: Permission denied. From docs-site without the custom build sequence, main.go can fail because //go:embed dist/site requires generated output to exist first.

The Blueprint now lives next to the docs-site service config and uses the same Root Directory shape as the Render UI: Root Directory docs-site, Build Command from docs-site/render.yaml, Start Command ./app.

Verification

  • git diff --cached --check
  • Created a minimal docs-site/dist/site/index.html and ran go build -tags netgo -ldflags '-s -w' -o app . from docs-site to verify the embed compile path once generated output exists.

Note: I did not run the full docs-site production build locally because the downloaded Tailwind standalone binary was killed by this macOS environment before GOWDK could run the CSS processor.

@cssbruno cssbruno force-pushed the codex/docs-site-render-build branch from df618fe to 8af6895 Compare June 20, 2026 19:52
@cssbruno cssbruno changed the title [codex] Share docs-site Render build command [codex] Move docs-site Render blueprint into docs-site Jun 20, 2026
@cssbruno cssbruno marked this pull request as ready for review June 20, 2026 19:54
@cssbruno cssbruno merged commit d5a4b28 into main Jun 20, 2026
16 checks passed
@cssbruno cssbruno deleted the codex/docs-site-render-build branch June 20, 2026 19:55

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8af689514c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs-site/render.yaml
- type: web
name: gowdk-page
runtime: go
rootDir: docs-site

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep the Render service rooted at the repository root

With rootDir: docs-site, Render's monorepo docs say "Files outside your service's root directory are not available" at build time (https://render.com/docs/monorepo-support). This build still depends on parent files: docs-site/go.mod replaces github.com/cssbruno/gowdk with ../, and syncdocs defaults GOWDK_SOURCE_ROOT to .. to read ../docs; in that Render environment, go run github.com/cssbruno/gowdk/cmd/gowdk build cannot resolve the replacement and docs generation cannot see the source docs. Leave the service rooted at the repo root and cd docs-site, or remove the parent-directory dependencies before setting rootDir.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant