github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-05-07 17:18:26 -05:00
Code Issues 1.2k Packages Projects Releases Wiki Activity

[PR #801] feat: add/update ZeroClaw template (v0.7.0-beta.1041) #2913

New Issue
Open
opened 2026-04-23 03:38:14 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-23 03:38:14 -05:00
Owner
Copy Link

📋 Pull Request Information

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

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

📝 Commits (1)

  • 6ab31ec feat: add/update ZeroClaw template (v0.7.0-beta.1041)

📊 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.0-beta.1041), a Rust-based autonomous AI assistant, following all blueprint conventions: correct docker-compose.yml structure, a valid template.toml with a generated 64-char API key, and a complete meta.json entry. The apparent removal of one Strapi entry in meta.json is the expected side-effect of deduplication — the base branch had two identical Strapi entries, and running dedupe-and-sort-meta.js collapsed them to one; Strapi remains in the registry.

Confidence Score: 5/5

Safe to merge — the template is well-formed and only the PNG-vs-SVG preference remains as a minor style note.

All required fields are present and consistent (version, logo filename, service name), conventions are followed (no ports/container_name/networks, restart policy, pinned image), and the only finding is a P2 logo-format suggestion that does not affect functionality.

No files require special attention.

Comments Outside Diff (1)

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

    P2 SVG preferred over PNG for logo

    AGENTS.md specifies "SVG preferred, ~128x128px" for blueprint logo files. A PNG will work but may appear blurry at high-DPI or when scaled in the UI. Consider converting to an SVG for crisper rendering.

    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.

## 📋 Pull Request Information **Original PR:** https://github.com/Dokploy/templates/pull/801 **Author:** [@theonlyhennygod](https://github.com/theonlyhennygod) **Created:** 4/17/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `zeroclaw/update-v0.7.0-beta.1041` --- ### 📝 Commits (1) - [`6ab31ec`](https://github.com/Dokploy/templates/commit/6ab31ece1cf1abb79beb054f83087050d8af3587) feat: add/update ZeroClaw template (v0.7.0-beta.1041) ### 📊 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.1041), a Rust-based autonomous AI assistant, following all blueprint conventions: correct `docker-compose.yml` structure, a valid `template.toml` with a generated 64-char API key, and a complete `meta.json` entry. The apparent removal of one Strapi entry in `meta.json` is the expected side-effect of deduplication — the base branch had two identical Strapi entries, and running `dedupe-and-sort-meta.js` collapsed them to one; Strapi remains in the registry. <h3>Confidence Score: 5/5</h3> Safe to merge — the template is well-formed and only the PNG-vs-SVG preference remains as a minor style note. All required fields are present and consistent (version, logo filename, service name), conventions are followed (no ports/container_name/networks, restart policy, pinned image), and the only finding is a P2 logo-format suggestion that does not affect functionality. No files require special attention. <!-- 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/6ab31ece1cf1abb79beb054f83087050d8af3587/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 specifies "SVG preferred, ~128x128px" for blueprint logo files. A PNG will work but may appear blurry at high-DPI or when scaled in the UI. Consider converting to an SVG for crisper rendering. 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/6ab31ece1cf1abb79beb054f83087050d8af3587) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28781049)</sub> <!-- /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-04-23 03:38:14 -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#2913
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?