Render deploy

[ojusave]

Add a Render Blueprint (render.yaml) and README deploy instructions so GoClaw can be deployed on Render with one click: official GHCR image, Postgres 18, persistent disk, and auto-generated gateway/encryption secrets.

Summary

Adds render.yaml for one-click Render deployment using the official ghcr.io/nextlevelbuilder/goclaw image, plus a short README section and badge-row link. The Blueprint wires Postgres 18, a 10GB persistent disk for agent workspaces, GOCLAW_PORT=10000 (GoClaw does not use Render's PORT), and generateValue for GOCLAW_GATEWAY_TOKEN and GOCLAW_ENCRYPTION_KEY. LLM provider keys are intentionally omitted from the Blueprint so Apply does not prompt for empty API keys.

Type

• Feature
• Bug fix
• Hotfix (targeting main)
• Refactor
• Docs
• CI/CD

Target Branch

dev

Checklist

• go build ./... passes — N/A, no Go changes
• go build -tags sqliteonly ./... passes (if Go changes) — N/A
• go vet ./... passes — N/A
• Tests pass: go test -race ./... — N/A
• Web UI builds: cd ui/web && pnpm build (if UI changes) — N/A
• No hardcoded secrets or credentials
• SQL queries use parameterized $1, $2 (no string concat) — N/A
• New user-facing strings added to all 3 locales (en/vi/zh) — N/A
• Migration version bumped in internal/upgrade/version.go (if new migration) — N/A

Test Plan

• Applied Blueprint from repo root; web service and Postgres 18 database provision successfully.
• Verified startup without dockerCommand shell wrapper (earlier dockerCommand caused exit 127); service binds on GOCLAW_PORT=10000 and passes /health.
• Confirmed migrations run on boot and create required extensions (no initialDeployHook / psql needed).
• Live deploy: https://goclaw-h5su.onrender.com — dashboard loads, gateway token auth works after copying GOCLAW_GATEWAY_TOKEN from Dashboard.
• Deploy button/badge links to https://render.com/deploy?repo=https://github.com/ojusave/goclaw&branch=dev.
• Post-deploy: add LLM provider API key in Settings (not required at Blueprint Apply time).

[mrgoonie]

Summary: This PR adds a useful Render one-click deployment path, but it is not upstream-ready because the Blueprint and README still point users at the contributor fork instead of nextlevelbuilder/goclaw, and the deployed image is pinned to a fixed release tag.

Risk level: Medium

Mandatory gates:

• Duplicate/prior implementation: clear; no existing Render Blueprint PR found in the current open queue.
• Project standards: issue found; upstream docs/deploy links must point at the upstream repo and avoid fork-specific guidance.
• Strategic necessity: clear value; Render deployment lowers adoption friction for hosted trials.
• CI/checks: missing/no checks reported; mergeState is UNSTABLE.

Findings:

• Important: README.md adds a Render badge linking to https://render.com/deploy?repo=https://github.com/ojusave/goclaw&branch=dev, and render.yaml comments also describe the Blueprint as being for https://github.com/ojusave/goclaw. That would send upstream users to a contributor fork from the official nextlevelbuilder/goclaw README. Please change all deploy/template links and comments to the upstream repo unless there is an explicit maintainer decision to publish the fork URL.
• Important: render.yaml pins image.url to ghcr.io/nextlevelbuilder/goclaw:v3.12.0. A repo Blueprint on dev should either use the intended moving release channel/tag documented by maintainers or clearly explain why a fixed historical tag is correct. As written, users applying the current repo Blueprint may deploy an older image that does not match the checked-out README/render.yaml.
• Important: No GitHub checks are reported for this branch. After the fork-link/image-tag issues are fixed, CI or a maintainer-acceptable docs/config validation path should run before merge.

Verdict: REQUEST_CHANGES

Next step: retarget the Render deploy URL/comments to nextlevelbuilder/goclaw, align the image tag with the intended upstream release channel, and re-request review once checks/validation are available.

Posted by /github-maintain at 2026-06-22T11:22:50Z