This PR adds a new ZeroClaw template (v0.7.0-beta.1047) with a docker-compose.yml, template.toml, logo, and meta.json entry. The blueprint itself follows Dokploy conventions correctly (version 3.8, expose over ports, named volumes, secret generation via ${password:64}), but the PR also inadvertently removes the existing Strapi entry from meta.json while the blueprints/strapi/ directory and all its files remain untouched.
The Strapi meta.json entry should be restored — its removal is unrelated to this PR and would silently hide Strapi from the template registry.
Confidence Score: 4/5
Not safe to merge until the accidental Strapi entry deletion from meta.json is reverted.
The ZeroClaw blueprint itself is well-formed, but the PR inadvertently removes an unrelated Strapi entry from meta.json, which would break Strapi's visibility in the template registry. This P1 issue must be fixed before merging.
meta.json — Strapi entry was accidentally removed and must be restored.
PNG logo; SVG preferred per contribution guidelines
AGENTS.md states "Add logo file (SVG preferred, ~128x128px) to blueprint folder." The current logo is a PNG file. Consider converting to SVG for better scaling and consistency with other templates.
🔄 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/804
**Author:** [@theonlyhennygod](https://github.com/theonlyhennygod)
**Created:** 4/18/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `zeroclaw/update-v0.7.0-beta.1047`
---
### 📝 Commits (1)
- [`dad9b35`](https://github.com/Dokploy/templates/commit/dad9b35ee2acea7b820c773bafb808ba0f8a4e2c) feat: add/update ZeroClaw template (v0.7.0-beta.1047)
### 📊 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 template (v0.7.0-beta.1047) with a `docker-compose.yml`, `template.toml`, logo, and `meta.json` entry. The blueprint itself follows Dokploy conventions correctly (version 3.8, `expose` over `ports`, named volumes, secret generation via `${password:64}`), but the PR also inadvertently removes the existing Strapi entry from `meta.json` while the `blueprints/strapi/` directory and all its files remain untouched.
- The Strapi `meta.json` entry should be restored — its removal is unrelated to this PR and would silently hide Strapi from the template registry.
<h3>Confidence Score: 4/5</h3>
Not safe to merge until the accidental Strapi entry deletion from meta.json is reverted.
The ZeroClaw blueprint itself is well-formed, but the PR inadvertently removes an unrelated Strapi entry from meta.json, which would break Strapi's visibility in the template registry. This P1 issue must be fixed before merging.
meta.json — Strapi entry was accidentally removed and must be restored.
<!-- greptile_failed_comments -->
<details><summary><h3>Comments Outside Diff (1)</h3></summary>
1. `blueprints/zeroclaw/zeroclaw.png`, line 1 ([link](https://github.com/dokploy/templates/blob/dad9b35ee2acea7b820c773bafb808ba0f8a4e2c/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 contribution guidelines**
AGENTS.md states "Add logo file (SVG preferred, ~128x128px) to blueprint folder." The current logo is a PNG file. Consider converting to SVG for better scaling and consistency with other templates.
**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/dad9b35ee2acea7b820c773bafb808ba0f8a4e2c) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28855073)</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/804
Author: @theonlyhennygod
Created: 4/18/2026
Status: 🔄 Open
Base:
main← Head:zeroclaw/update-v0.7.0-beta.1047📝 Commits (1)
dad9b35feat: add/update ZeroClaw template (v0.7.0-beta.1047)📊 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 template (v0.7.0-beta.1047) with a
docker-compose.yml,template.toml, logo, andmeta.jsonentry. The blueprint itself follows Dokploy conventions correctly (version 3.8,exposeoverports, named volumes, secret generation via${password:64}), but the PR also inadvertently removes the existing Strapi entry frommeta.jsonwhile theblueprints/strapi/directory and all its files remain untouched.meta.jsonentry should be restored — its removal is unrelated to this PR and would silently hide Strapi from the template registry.Confidence Score: 4/5
Not safe to merge until the accidental Strapi entry deletion from meta.json is reverted.
The ZeroClaw blueprint itself is well-formed, but the PR inadvertently removes an unrelated Strapi entry from meta.json, which would break Strapi's visibility in the template registry. This P1 issue must be fixed before merging.
meta.json — Strapi entry was accidentally removed and must be restored.
Comments Outside Diff (1)
blueprints/zeroclaw/zeroclaw.png, line 1 (link)AGENTS.md states "Add logo file (SVG preferred, ~128x128px) to blueprint folder." The current logo is a PNG file. Consider converting to SVG for better scaling and consistency with other templates.
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.