github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-05-22 06:23:58 -05:00
Code Issues 1.7k Packages Projects Releases Wiki Activity

[PR #797] [CLOSED] feat: add/update ZeroClaw template (v0.7.0-beta.1040) #5105

New Issue
Closed
opened 2026-05-06 17:57:26 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-06 17:57:26 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/797
Author: @theonlyhennygod
Created: 4/17/2026
Status: ❌ Closed

Base: main ← Head: zeroclaw/update-v0.7.0-beta.1040

📝 Commits (1)

  • 7311e39 feat: add/update ZeroClaw template (v0.7.0-beta.1040)

📊 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 the ZeroClaw (v0.7.0-beta.1040) template — a self-hosted, Rust-based autonomous AI assistant. The blueprint structure, docker-compose.yml, and meta.json entry are all correct, and the Strapi removal visible in the diff is the deduplication script legitimately removing a pre-existing duplicate entry.

  • P1 — API_KEY is the LLM provider credential, not a gateway key. Per ZeroClaw's official environment variable docs, API_KEY is the "Primary provider API key." Setting it to ${password:64} (a random 64-char string) causes the service to start and pass health checks, but every AI call will fail with an authentication error from the provider. The user's real OpenRouter (or other provider) API key must be supplied — it should not be auto-generated.

Confidence Score: 4/5

Mergeable after fixing the API_KEY variable — as-is the service boots but all AI functionality is broken.

One P1 finding: auto-generating the primary LLM provider API key as a random password means any deployment from this template will start but be non-functional for AI tasks. The rest of the blueprint follows all Dokploy conventions correctly.

blueprints/zeroclaw/template.toml — api_key variable definition needs to accept user-provided value instead of auto-generating.

Comments Outside Diff (1)

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

    P2 PNG logo instead of preferred SVG format

    The project guidelines specify "SVG preferred, ~128x128px" for template logos. Using PNG works, but an SVG would scale cleanly at all resolutions in the Dokploy UI.

    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.

🔄 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/797 **Author:** [@theonlyhennygod](https://github.com/theonlyhennygod) **Created:** 4/17/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `zeroclaw/update-v0.7.0-beta.1040` --- ### 📝 Commits (1) - [`7311e39`](https://github.com/Dokploy/templates/commit/7311e39b4577ebe2834932e760d8d8f550d7b6f2) feat: add/update ZeroClaw template (v0.7.0-beta.1040) ### 📊 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 the ZeroClaw (v0.7.0-beta.1040) template — a self-hosted, Rust-based autonomous AI assistant. The blueprint structure, `docker-compose.yml`, and `meta.json` entry are all correct, and the Strapi removal visible in the diff is the deduplication script legitimately removing a pre-existing duplicate entry. - **P1 — `API_KEY` is the LLM provider credential, not a gateway key.** Per ZeroClaw's [official environment variable docs](https://github.com/zeroclaw-labs/zeroclaw/wiki/04.2-Environment-Variables), `API_KEY` is the \"Primary provider API key.\" Setting it to `${password:64}` (a random 64-char string) causes the service to start and pass health checks, but every AI call will fail with an authentication error from the provider. The user's real OpenRouter (or other provider) API key must be supplied — it should not be auto-generated. <h3>Confidence Score: 4/5</h3> Mergeable after fixing the API_KEY variable — as-is the service boots but all AI functionality is broken. One P1 finding: auto-generating the primary LLM provider API key as a random password means any deployment from this template will start but be non-functional for AI tasks. The rest of the blueprint follows all Dokploy conventions correctly. blueprints/zeroclaw/template.toml — api_key variable definition needs to accept user-provided value instead of auto-generating. <!-- 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/7311e39b4577ebe2834932e760d8d8f550d7b6f2/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 format** The project guidelines specify "SVG preferred, ~128x128px" for template logos. Using PNG works, but an SVG would scale cleanly at all resolutions in the Dokploy UI. 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/7311e39b4577ebe2834932e760d8d8f550d7b6f2) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28746243)</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>
GiteaMirror added the pull-request label 2026-05-06 17:57:26 -05:00
GiteaMirror changed title from [PR #797] feat: add/update ZeroClaw template (v0.7.0-beta.1040) to [PR #797] [CLOSED] feat: add/update ZeroClaw template (v0.7.0-beta.1040) 2026-05-13 19:58:06 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#5105
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?