[PR #780] feat: add/update ZeroClaw template (v0.6.9) #2091

New Issue

GiteaMirror · 2026-04-20T11:06:01-05:00

GiteaMirror commented

2026-04-20 11:06:01 -05:00

📋 Pull Request Information

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

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

📝 Commits (1)

d860b33 feat: add/update ZeroClaw template (v0.6.9)

📊 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.6.9) — a Rust-based autonomous AI assistant — following the standard Dokploy template structure. The docker-compose.yml and template.toml are well-formed, the meta.json entry is complete and correctly versioned, and the removed Strapi block was a duplicate (the canonical entry is preserved).

Confidence Score: 5/5

Safe to merge; all remaining findings are minor style suggestions.

Both new files follow AGENTS.md conventions (version 3.8, expose not ports, restart policy, pinned image, named volume). The only findings are P2: PNG logo instead of preferred SVG, and PROVIDER not exposed as a configurable template variable. Neither affects correctness or deployment reliability.

No files require special attention.

Vulnerabilities

No security concerns identified. The API_KEY is auto-generated using Dokploy's ${password:64} helper (not hardcoded). Docker image is pinned to a specific version (0.6.9). ZEROCLAW_ALLOW_PUBLIC_BIND=true is intentional and appropriate given that Dokploy's reverse proxy handles external exposure.

Comments Outside Diff (1)

blueprints/zeroclaw/zeroclaw.png, line 1 (link)

PNG logo instead of preferred SVG

The AGENTS.md style guide specifies "SVG preferred, ~128x128px" for blueprint logos. The submitted logo is a .png file. This isn't a hard blocker, but converting or providing an SVG version would align with the project's stated convention and typically yields a sharper result in the UI at any scale.

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.6..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

_{(5/5) You can turn off certain types of comments like style here!}

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/780 **Author:** [@theonlyhennygod](https://github.com/theonlyhennygod) **Created:** 4/8/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `zeroclaw/update-v0.6.9` --- ### 📝 Commits (1) - [`d860b33`](https://github.com/Dokploy/templates/commit/d860b332a10d7a4eac613486ed7196a9c79f1dfe) feat: add/update ZeroClaw template (v0.6.9) ### 📊 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.6.9) — a Rust-based autonomous AI assistant — following the standard Dokploy template structure. The `docker-compose.yml` and `template.toml` are well-formed, the `meta.json` entry is complete and correctly versioned, and the removed Strapi block was a duplicate (the canonical entry is preserved). <h3>Confidence Score: 5/5</h3> Safe to merge; all remaining findings are minor style suggestions. Both new files follow AGENTS.md conventions (version 3.8, expose not ports, restart policy, pinned image, named volume). The only findings are P2: PNG logo instead of preferred SVG, and PROVIDER not exposed as a configurable template variable. Neither affects correctness or deployment reliability. No files require special attention. <details open><summary><h3>Vulnerabilities</h3></summary> No security concerns identified. The `API_KEY` is auto-generated using Dokploy's `${password:64}` helper (not hardcoded). Docker image is pinned to a specific version (`0.6.9`). `ZEROCLAW_ALLOW_PUBLIC_BIND=true` is intentional and appropriate given that Dokploy's reverse proxy handles external exposure. </details>  <details><summary><h3>Comments Outside Diff (1)</h3></summary> 1. `blueprints/zeroclaw/zeroclaw.png`, line 1 ([link](https://github.com/dokploy/templates/blob/d860b332a10d7a4eac613486ed7196a9c79f1dfe/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 instead of preferred SVG** The AGENTS.md style guide specifies "SVG preferred, ~128x128px" for blueprint logos. The submitted logo is a `.png` file. This isn't a hard blocker, but converting or providing an SVG version would align with the project's stated convention and typically yields a sharper result in the UI at any scale. **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.6..."](https://github.com/dokploy/templates/commit/d860b332a10d7a4eac613486ed7196a9c79f1dfe) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=27737844)</sub> > Greptile also left **1 inline comment** on this PR. <sub>(5/5) You can turn off certain types of comments like style [here](https://app.greptile.com/review/github)!</sub> **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-20 11:06:01 -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#2091