feat: add/update ZeroClaw template (v0.7.1-beta.1045)#803
feat: add/update ZeroClaw template (v0.7.1-beta.1045)#803theonlyhennygod wants to merge 1 commit intoDokploy:mainfrom
Conversation
dosubot
bot
added
size:S
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| @@ -5952,24 +5952,6 @@ | |||
| "media" | |||
There was a problem hiding this comment.
The Strapi template entry was deleted from meta.json in this PR, but blueprints/strapi/ still contains all three blueprint files (docker-compose.yml, template.toml, strapi.svg). This removal appears to be an accidental conflict/rebase artifact — it would silently drop Strapi from the template registry, making it undiscoverable without any corresponding cleanup of the blueprint files.
| @@ -0,0 +1,16 @@ | |||
| [variables] | |||
| main_domain = "${domain}" | |||
| api_key = "${password:64}" | |||
There was a problem hiding this comment.
${password:64} generates a random 64-character string and injects it as API_KEY. Based on the project description and the PROVIDER=openrouter default, this variable is the user's real AI provider credential (e.g. an OpenRouter key). A randomly-generated value will never authenticate against any provider, so the assistant will silently fail on first use. The variable should be left empty or use a placeholder that prompts the user to supply their actual key.
| restart: unless-stopped | ||
| environment: | ||
| - API_KEY=${API_KEY} | ||
| - PROVIDER=${PROVIDER:-openrouter} |
There was a problem hiding this comment.
The docker-compose.yml uses ${PROVIDER:-openrouter} (shell default substitution), while template.toml hardcodes PROVIDER=openrouter unconditionally. The template.toml env array takes precedence during Dokploy deployment, so the shell default in the Compose file is effectively unused. Aligning both to the same plain form avoids confusion:
| - PROVIDER=${PROVIDER:-openrouter} | |
| - PROVIDER=${PROVIDER} |
1 participant
Summary
ghcr.io/zeroclaw-labs/zeroclaw:${VERSION}Checklist
Testing
Links
Greptile Summary
This PR adds the ZeroClaw AI assistant template (v0.7.1-beta.1045) with a
docker-compose.yml,template.toml, logo, andmeta.jsonentry. The blueprint structure is mostly correct, but two issues need addressing before merge:meta.json— its blueprint files are untouched, so this appears to be a rebase/merge artifact that would drop Strapi from the template registry.API_KEYis set to a randomly-generated 64-character password via${password:64}, but ZeroClaw uses this as the user's real AI provider credential (e.g. OpenRouter); a generated value will never authenticate and the assistant won't function.Confidence Score: 3/5
Not safe to merge — two P1 issues: unintentional removal of the Strapi template and an auto-generated value for a required AI provider API key.
Both findings are present defects on the changed path: the Strapi deletion breaks an existing template's discoverability, and the auto-generated API_KEY will prevent ZeroClaw from connecting to any AI provider on first deploy.
meta.json(Strapi removal) andblueprints/zeroclaw/template.toml(API_KEY generation)Reviews (1): Last reviewed commit: "feat: add/update ZeroClaw template (v0.7..." | Re-trigger Greptile