Render deploy#1181
Open
ojusave wants to merge 6 commits into
Open
Conversation
Render parsed the shell one-liner as a single binary path (exit 127). Use GOCLAW_PORT=10000 instead. Remove initialDeployHook; migrations create pgvector/pgcrypto and the image has no psql client.
Pin image to v3.12.0, set GOCLAW_PORT=10000 explicitly, remove dockerCommand and initialDeployHook (both caused deploy failures), drop optional provider keys from Apply UI, add shutdown delay and document port contract in comments.
Move deploy link to a flat badge beside Docker; replace hero button and long deploy section with a short pointer to render.yaml.
Replace custom shields.io badge with render.com/images/deploy-to-render-button.svg sized inline after Docker.
Replace the full Deploy to Render SVG with a flat-square shields badge so it matches Go, Docker, and the other row badges.
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.
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.yamlfor one-click Render deployment using the officialghcr.io/nextlevelbuilder/goclawimage, 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'sPORT), andgenerateValueforGOCLAW_GATEWAY_TOKENandGOCLAW_ENCRYPTION_KEY. LLM provider keys are intentionally omitted from the Blueprint so Apply does not prompt for empty API keys.Type
main)Target Branch
devChecklist
go build ./...passes — N/A, no Go changesgo build -tags sqliteonly ./...passes (if Go changes) — N/Ago vet ./...passes — N/Ago test -race ./...— N/Acd ui/web && pnpm build(if UI changes) — N/A$1,$2(no string concat) — N/Ainternal/upgrade/version.go(if new migration) — N/ATest Plan
dockerCommandshell wrapper (earlierdockerCommandcaused exit 127); service binds onGOCLAW_PORT=10000and passes/health.initialDeployHook/psqlneeded).https://goclaw-h5su.onrender.com— dashboard loads, gateway token auth works after copyingGOCLAW_GATEWAY_TOKENfrom Dashboard.https://render.com/deploy?repo=https://github.com/ojusave/goclaw&branch=dev.