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

[PR #796] feat: add/update ZeroClaw template (v0.7.0-beta.1030) #2908

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

📋 Pull Request Information

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

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

📝 Commits (1)

  • 3558b4a feat: add/update ZeroClaw template (v0.7.0-beta.1030)

📊 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 template (v0.7.0-beta.1030) — a Rust-based AI assistant. The new blueprint files (docker-compose.yml, template.toml, logo) are well-formed and follow repository conventions, but the meta.json diff also removes the existing Strapi template entry, which appears unintentional and would break Strapi availability for all Dokploy users.

  • P1: The strapi entry is deleted from meta.json with no explanation. This looks like a merge conflict artifact and should be restored before merging.

Confidence Score: 4/5

Not safe to merge until the accidental Strapi deletion from meta.json is reverted.

The ZeroClaw blueprint itself is correct and complete, but the unintended removal of the Strapi entry from meta.json is a present defect that would silently break an existing well-known template for all users.

meta.json — the Strapi entry deletion must be reverted.

Comments Outside Diff (2)

  1. meta.json, line 5952-5958 (link)

    P1 Unintended removal of Strapi template entry

    The PR removes the entire strapi entry from meta.json (18 lines deleted starting at the original line 5955), but the PR description and title make no mention of removing Strapi. This looks like a merge conflict artifact or accidental deletion. Removing it would make the Strapi template unavailable in the registry for all Dokploy users.

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

    P2 Logo should be SVG (preferred) per project conventions

    The AGENTS.md style guide states "SVG preferred, ~128x128px" for blueprint logos. A PNG will work but an SVG would scale better across different display sizes and is the expected format for this repository.

    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/796 **Author:** [@theonlyhennygod](https://github.com/theonlyhennygod) **Created:** 4/17/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `zeroclaw/update-v0.7.0-beta.1030` --- ### 📝 Commits (1) - [`3558b4a`](https://github.com/Dokploy/templates/commit/3558b4acc80384d2e4828713f19abc999414defb) feat: add/update ZeroClaw template (v0.7.0-beta.1030) ### 📊 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 template (v0.7.0-beta.1030) — a Rust-based AI assistant. The new blueprint files (`docker-compose.yml`, `template.toml`, logo) are well-formed and follow repository conventions, but the `meta.json` diff also removes the existing **Strapi** template entry, which appears unintentional and would break Strapi availability for all Dokploy users. - **P1**: The `strapi` entry is deleted from `meta.json` with no explanation. This looks like a merge conflict artifact and should be restored before merging. <h3>Confidence Score: 4/5</h3> Not safe to merge until the accidental Strapi deletion from meta.json is reverted. The ZeroClaw blueprint itself is correct and complete, but the unintended removal of the Strapi entry from meta.json is a present defect that would silently break an existing well-known template for all users. meta.json — the Strapi entry deletion must be reverted. <!-- greptile_failed_comments --> <details><summary><h3>Comments Outside Diff (2)</h3></summary> 1. `meta.json`, line 5952-5958 ([link](https://github.com/dokploy/templates/blob/3558b4acc80384d2e4828713f19abc999414defb/meta.json#L5952-L5958)) <a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **Unintended removal of Strapi template entry** The PR removes the entire `strapi` entry from `meta.json` (18 lines deleted starting at the original line 5955), but the PR description and title make no mention of removing Strapi. This looks like a merge conflict artifact or accidental deletion. Removing it would make the Strapi template unavailable in the registry for all Dokploy users. 2. `blueprints/zeroclaw/zeroclaw.png`, line 1 ([link](https://github.com/dokploy/templates/blob/3558b4acc80384d2e4828713f19abc999414defb/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> **Logo should be SVG (preferred) per project conventions** The AGENTS.md style guide states "SVG preferred, ~128x128px" for blueprint logos. A PNG will work but an SVG would scale better across different display sizes and is the expected format for this repository. 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/3558b4acc80384d2e4828713f19abc999414defb) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28730798)</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-04-23 03:38: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#2908
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?