[PR #802] feat: add/update ZeroClaw template (v0.7.1) #4274

New Issue

GiteaMirror · 2026-04-30T06:51:07-05:00

GiteaMirror commented

2026-04-30 06:51:07 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/802
Author: @theonlyhennygod
Created: 4/18/2026
Status: 🔄 Open

Base: main ← Head: zeroclaw/update-v0.7.1

📝 Commits (1)

2681f82 feat: add/update ZeroClaw template (v0.7.1)

📊 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

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

Read README.md suggestions
Tested template in personal Dokploy instance
Confirmed all requirements met

Testing

Deployed via Compose service import
Service starts and gateway is accessible on port 42617
Health check passes

Links

Greptile Summary

This PR adds a new ZeroClaw blueprint (v0.7.1) for a Rust-based autonomous AI assistant. The compose file and template structure are well-formed and follow conventions, but two issues need attention before merging.

Strapi removed from meta.json: The diff deletes the entire strapi entry — Strapi's blueprint files still exist but it becomes invisible in the registry. This appears to be an unintended merge/rebase artifact and must be restored.
API_KEY is auto-generated: ZeroClaw connects to an external AI provider (PROVIDER=openrouter), and API_KEY is almost certainly the user's provider credential. Generating a random value will cause authentication failures at startup; the user should supply their own key.

Confidence Score: 4/5

Not safe to merge until the unintended Strapi removal and the auto-generated API key issue are resolved.

Two P1 findings: the Strapi meta.json entry is silently dropped (breaking that template's discoverability), and the API_KEY is auto-generated in a way that will likely cause ZeroClaw to fail connecting to its AI provider. Both need to be addressed before merging.

meta.json (Strapi removal) and blueprints/zeroclaw/template.toml (API_KEY generation)

Comments Outside Diff (2)

meta.json, line 5952-5971 (link)

Strapi entry unintentionally removed

The diff removes the entire strapi entry from meta.json but the PR is only meant to add/update ZeroClaw. Strapi's blueprint files still exist in the repository — removing it from meta.json makes it invisible to users of the template registry. This looks like an accidental conflict/rebase artifact and needs to be restored.
blueprints/zeroclaw/zeroclaw.png, line 1 (link)

SVG preferred over PNG for logo

AGENTS.md states "Add logo file (SVG preferred, ~128x128px) to blueprint folder." Using a PNG is not a hard blocker, but an SVG would scale better across the Dokploy UI. Consider replacing with an SVG if one is available upstream.

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}

Greptile also left 1 inline comment on this PR.

Context used:

Context used - AGENTS.md (source)

_{🔄 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/802 **Author:** [@theonlyhennygod](https://github.com/theonlyhennygod) **Created:** 4/18/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `zeroclaw/update-v0.7.1` --- ### 📝 Commits (1) - [`2681f82`](https://github.com/Dokploy/templates/commit/2681f821542a6e1409f1da1788aa4ce6449027d6) feat: add/update ZeroClaw template (v0.7.1) ### 📊 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  <h3>Greptile Summary</h3> This PR adds a new ZeroClaw blueprint (v0.7.1) for a Rust-based autonomous AI assistant. The compose file and template structure are well-formed and follow conventions, but two issues need attention before merging. - **Strapi removed from `meta.json`**: The diff deletes the entire `strapi` entry — Strapi's blueprint files still exist but it becomes invisible in the registry. This appears to be an unintended merge/rebase artifact and must be restored. - **`API_KEY` is auto-generated**: ZeroClaw connects to an external AI provider (`PROVIDER=openrouter`), and `API_KEY` is almost certainly the user's provider credential. Generating a random value will cause authentication failures at startup; the user should supply their own key. <h3>Confidence Score: 4/5</h3> Not safe to merge until the unintended Strapi removal and the auto-generated API key issue are resolved. Two P1 findings: the Strapi meta.json entry is silently dropped (breaking that template's discoverability), and the API_KEY is auto-generated in a way that will likely cause ZeroClaw to fail connecting to its AI provider. Both need to be addressed before merging. meta.json (Strapi removal) and blueprints/zeroclaw/template.toml (API_KEY generation)  <details><summary><h3>Comments Outside Diff (2)</h3></summary> 1. `meta.json`, line 5952-5971 ([link](https://github.com/dokploy/templates/blob/2681f821542a6e1409f1da1788aa4ce6449027d6/meta.json#L5952-L5971)) <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 diff removes the entire `strapi` entry from `meta.json` but the PR is only meant to add/update ZeroClaw. Strapi's blueprint files still exist in the repository — removing it from `meta.json` makes it invisible to users of the template registry. This looks like an accidental conflict/rebase artifact and needs to be restored. 2. `blueprints/zeroclaw/zeroclaw.png`, line 1 ([link](https://github.com/dokploy/templates/blob/2681f821542a6e1409f1da1788aa4ce6449027d6/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> **SVG preferred over PNG for logo** `AGENTS.md` states "Add logo file (SVG preferred, ~128x128px) to blueprint folder." Using a PNG is not a hard blocker, but an SVG would scale better across the Dokploy UI. Consider replacing with an SVG if one is available upstream. **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>  <sub>Reviews (1): Last reviewed commit: ["feat: add/update ZeroClaw template (v0.7..."](https://github.com/dokploy/templates/commit/2681f821542a6e1409f1da1788aa4ce6449027d6) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28852384)</sub> > Greptile also left **1 inline comment** on this PR. **Context used:** - Context used - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))  --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-30 06:51:07 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#4274