This PR adds a new ZeroClaw blueprint (v0.7.3-beta.1051) with a docker-compose, template.toml, logo, and meta.json entry. Two blocking issues exist: the Strapi entry has been accidentally deleted from meta.json (its blueprint files are still present), and the API_KEY for the LLM provider is populated with an auto-generated random string rather than a real user-supplied provider credential, which will cause the service to fail on first use.
Confidence Score: 3/5
Not safe to merge — accidental Strapi removal breaks an existing template, and the API_KEY misconfiguration will cause ZeroClaw to fail on first use.
Two P1 issues are present: the unintended removal of the Strapi registry entry (which breaks an existing template for all users) and the incorrect use of a generated password as the user's external LLM provider API key. Both need to be fixed before this can be merged.
meta.json (Strapi removal) and blueprints/zeroclaw/template.toml (API_KEY generation)
The strapi entry has been deleted from meta.json, but blueprints/strapi/ (with docker-compose.yml, template.toml, strapi.svg) still exists on disk. Removing it from the registry makes Strapi invisible in the Dokploy template browser while its blueprint files remain, leaving it in a broken/orphaned state. This change is not mentioned in the PR description and appears accidental — likely caused by a merge conflict or a stale meta.json base. The entry should be restored.
Per project conventions, logo files should be SVG (~128×128 px) for sharper rendering at all sizes. PNG will work but is not the preferred format. If an SVG source is available, swapping it in would be better.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/Dokploy/templates/pull/809
**Author:** [@theonlyhennygod](https://github.com/theonlyhennygod)
**Created:** 4/19/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `zeroclaw/update-v0.7.3-beta.1051`
---
### 📝 Commits (1)
- [`3c8b750`](https://github.com/Dokploy/templates/commit/3c8b7508c0c203b0810b3ac17d9e431842663407) feat: add/update ZeroClaw template (v0.7.3-beta.1051)
### 📊 Changes
**4 files changed** (+48 additions, -18 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/zeroclaw/docker-compose.yml` (+16 -0)
➕ `blueprints/zeroclaw/template.toml` (+16 -0)
➕ `blueprints/zeroclaw/zeroclaw.png` (+0 -0)
📝 `meta.json` (+16 -18)
</details>
### 📄 Description
## Summary
- Adds/updates ZeroClaw template to v${VERSION}
- Image: `ghcr.io/zeroclaw-labs/zeroclaw:${VERSION}`
- ZeroClaw is a fast, small, fully autonomous AI personal assistant (100% Rust)
- Multi-arch: linux/amd64 + linux/arm64
## Checklist
- [x] Read README.md suggestions
- [x] Tested template in personal Dokploy instance
- [x] Confirmed all requirements met
## Testing
- Deployed via Compose service import
- Service starts and gateway is accessible on port 42617
- Health check passes
## Links
- https://github.com/zeroclaw-labs/zeroclaw
- https://github.com/orgs/zeroclaw-labs/packages/container/package/zeroclaw
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR adds a new ZeroClaw blueprint (v0.7.3-beta.1051) with a docker-compose, template.toml, logo, and `meta.json` entry. Two blocking issues exist: the Strapi entry has been accidentally deleted from `meta.json` (its blueprint files are still present), and the `API_KEY` for the LLM provider is populated with an auto-generated random string rather than a real user-supplied provider credential, which will cause the service to fail on first use.
<h3>Confidence Score: 3/5</h3>
Not safe to merge — accidental Strapi removal breaks an existing template, and the API_KEY misconfiguration will cause ZeroClaw to fail on first use.
Two P1 issues are present: the unintended removal of the Strapi registry entry (which breaks an existing template for all users) and the incorrect use of a generated password as the user's external LLM provider API key. Both need to be fixed before this can be merged.
`meta.json` (Strapi removal) and `blueprints/zeroclaw/template.toml` (API_KEY generation)
<!-- greptile_failed_comments -->
<details><summary><h3>Comments Outside Diff (2)</h3></summary>
1. `meta.json`, line 5952-5969 ([link](https://github.com/dokploy/templates/blob/3c8b7508c0c203b0810b3ac17d9e431842663407/meta.json#L5952-L5969))
<a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **Strapi entry unintentionally removed**
The `strapi` entry has been deleted from `meta.json`, but `blueprints/strapi/` (with `docker-compose.yml`, `template.toml`, `strapi.svg`) still exists on disk. Removing it from the registry makes Strapi invisible in the Dokploy template browser while its blueprint files remain, leaving it in a broken/orphaned state. This change is not mentioned in the PR description and appears accidental — likely caused by a merge conflict or a stale `meta.json` base. The entry should be restored.
2. `blueprints/zeroclaw/zeroclaw.png`, line 1 ([link](https://github.com/dokploy/templates/blob/3c8b7508c0c203b0810b3ac17d9e431842663407/blueprints/zeroclaw/zeroclaw.png#L1))
<a href="#"><img alt="P2" src="https://greptile-static-assets.s3.amazonaws.com/badges/p2.svg?v=7" align="top"></a> **PNG logo — SVG preferred**
Per project conventions, logo files should be SVG (~128×128 px) for sharper rendering at all sizes. PNG will work but is not the preferred format. If an SVG source is available, swapping it in would be better.
**Context Used:** AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
</details>
<!-- /greptile_failed_comments -->
<sub>Reviews (1): Last reviewed commit: ["feat: add/update ZeroClaw template (v0.7..."](https://github.com/dokploy/templates/commit/3c8b7508c0c203b0810b3ac17d9e431842663407) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28887319)</sub>
> Greptile also left **1 inline comment** on this PR.
<!-- /greptile_comment -->
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/809
Author: @theonlyhennygod
Created: 4/19/2026
Status: 🔄 Open
Base:
main← Head:zeroclaw/update-v0.7.3-beta.1051📝 Commits (1)
3c8b750feat: add/update ZeroClaw template (v0.7.3-beta.1051)📊 Changes
4 files changed (+48 additions, -18 deletions)
View changed files
➕
blueprints/zeroclaw/docker-compose.yml(+16 -0)➕
blueprints/zeroclaw/template.toml(+16 -0)➕
blueprints/zeroclaw/zeroclaw.png(+0 -0)📝
meta.json(+16 -18)📄 Description
Summary
ghcr.io/zeroclaw-labs/zeroclaw:${VERSION}Checklist
Testing
Links
Greptile Summary
This PR adds a new ZeroClaw blueprint (v0.7.3-beta.1051) with a docker-compose, template.toml, logo, and
meta.jsonentry. Two blocking issues exist: the Strapi entry has been accidentally deleted frommeta.json(its blueprint files are still present), and theAPI_KEYfor the LLM provider is populated with an auto-generated random string rather than a real user-supplied provider credential, which will cause the service to fail on first use.Confidence Score: 3/5
Not safe to merge — accidental Strapi removal breaks an existing template, and the API_KEY misconfiguration will cause ZeroClaw to fail on first use.
Two P1 issues are present: the unintended removal of the Strapi registry entry (which breaks an existing template for all users) and the incorrect use of a generated password as the user's external LLM provider API key. Both need to be fixed before this can be merged.
meta.json(Strapi removal) andblueprints/zeroclaw/template.toml(API_KEY generation)Comments Outside Diff (2)
meta.json, line 5952-5969 (link)The
strapientry has been deleted frommeta.json, butblueprints/strapi/(withdocker-compose.yml,template.toml,strapi.svg) still exists on disk. Removing it from the registry makes Strapi invisible in the Dokploy template browser while its blueprint files remain, leaving it in a broken/orphaned state. This change is not mentioned in the PR description and appears accidental — likely caused by a merge conflict or a stalemeta.jsonbase. The entry should be restored.blueprints/zeroclaw/zeroclaw.png, line 1 (link)Per project conventions, logo files should be SVG (~128×128 px) for sharper rendering at all sizes. PNG will work but is not the preferred format. If an SVG source is available, swapping it in would be better.
Context Used: AGENTS.md (source)
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Reviews (1): Last reviewed commit: "feat: add/update ZeroClaw template (v0.7..." | Re-trigger Greptile
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.