[PR #807] feat: add/update ZeroClaw template (v0.7.1-beta.1049) #4279

New Issue

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

GiteaMirror commented

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

📋 Pull Request Information

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

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

📝 Commits (1)

820205a feat: add/update ZeroClaw template (v0.7.1-beta.1049)

📊 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 template (v0.7.1-beta.1049) with a docker-compose.yml, template.toml, logo, and meta.json entry. However, it also unintentionally removes the existing Strapi entry from meta.json while Strapi's blueprint files remain on disk, and the API_KEY variable is auto-generated rather than accepting user input, which will likely break LLM provider authentication on every deployment.

Strapi removed from meta.json — blueprints/strapi/ still exists; the registry entry must be restored.
API_KEY auto-generated — with PROVIDER=openrouter, this is almost certainly an external provider credential that must be supplied by the user, not randomly generated.

Confidence Score: 3/5

Not safe to merge — removes an existing template from the registry and likely ships a non-functional API key configuration.

Two P1 issues: the Strapi entry is silently dropped from meta.json (orphaning its blueprint files), and the auto-generated API_KEY will break LLM provider authentication for every ZeroClaw deployment. Both must be resolved 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 Strapi template entry is deleted from meta.json, but its blueprint files (blueprints/strapi/docker-compose.yml, template.toml, strapi.svg) still exist. This leaves Strapi's compose files orphaned and invisible in the template registry. This looks like an accidental side-effect — likely caused by running dedupe-and-sort-meta.js in a state where Strapi was already absent, or a merge conflict resolution that dropped the block. The Strapi entry should be restored.
blueprints/zeroclaw/zeroclaw.png, line 1 (link)

SVG preferred over PNG for logo

Per project conventions, logo files should be SVG (~128×128 px) for crisp rendering at all sizes. A PNG will work but may appear blurry in the UI at higher DPI. Consider providing an SVG version.

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/807 **Author:** [@theonlyhennygod](https://github.com/theonlyhennygod) **Created:** 4/18/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `zeroclaw/update-v0.7.1-beta.1049` --- ### 📝 Commits (1) - [`820205a`](https://github.com/Dokploy/templates/commit/820205a1e05b4af70a6e6db57dbdf07fdedb1188) feat: add/update ZeroClaw template (v0.7.1-beta.1049) ### 📊 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 template (v0.7.1-beta.1049) with a `docker-compose.yml`, `template.toml`, logo, and `meta.json` entry. However, it also unintentionally removes the existing Strapi entry from `meta.json` while Strapi's blueprint files remain on disk, and the `API_KEY` variable is auto-generated rather than accepting user input, which will likely break LLM provider authentication on every deployment. - **Strapi removed from `meta.json`** — `blueprints/strapi/` still exists; the registry entry must be restored. - **`API_KEY` auto-generated** — with `PROVIDER=openrouter`, this is almost certainly an external provider credential that must be supplied by the user, not randomly generated. <h3>Confidence Score: 3/5</h3> Not safe to merge — removes an existing template from the registry and likely ships a non-functional API key configuration. Two P1 issues: the Strapi entry is silently dropped from meta.json (orphaning its blueprint files), and the auto-generated API_KEY will break LLM provider authentication for every ZeroClaw deployment. Both must be resolved 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/820205a1e05b4af70a6e6db57dbdf07fdedb1188/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 Strapi template entry is deleted from `meta.json`, but its blueprint files (`blueprints/strapi/docker-compose.yml`, `template.toml`, `strapi.svg`) still exist. This leaves Strapi's compose files orphaned and invisible in the template registry. This looks like an accidental side-effect — likely caused by running `dedupe-and-sort-meta.js` in a state where Strapi was already absent, or a merge conflict resolution that dropped the block. The Strapi entry should be restored. 2. `blueprints/zeroclaw/zeroclaw.png`, line 1 ([link](https://github.com/dokploy/templates/blob/820205a1e05b4af70a6e6db57dbdf07fdedb1188/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** Per project conventions, logo files should be SVG (~128×128 px) for crisp rendering at all sizes. A PNG will work but may appear blurry in the UI at higher DPI. Consider providing an SVG version. **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/820205a1e05b4af70a6e6db57dbdf07fdedb1188) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28878963)</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:17 -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#4279