github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-07-16 21:58:44 -05:00
Code Issues 3.0k Packages Projects Releases Wiki Activity

[PR #762] [CLOSED] feat: add/update ZeroClaw template (v0.6.7) #8670

New Issue
Closed
opened 2026-05-29 03:36:55 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-29 03:36:55 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/762
Author: @theonlyhennygod
Created: 3/29/2026
Status: ❌ Closed

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

📝 Commits (1)

  • 6873dbc feat: add/update ZeroClaw template (v0.6.7)

📊 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.6.7) — a Rust-based AI personal assistant — to the Dokploy template registry. The docker-compose.yml is well-structured and follows all repository conventions. However, two issues need to be addressed before merging:

  • Accidental Strapi removal: The strapi entry was deleted from meta.json even though its blueprint folder (blueprints/strapi/) still exists. This is unrelated to the ZeroClaw addition and appears to be an accidental side-effect, likely from a merge conflict resolution or running the sort script against a dirty tree. Restoring it is required.
  • AI provider key generated as random password: template.toml uses ${password:64} to auto-generate the API_KEY, but this variable holds the user's upstream AI provider credential (OpenRouter, OpenAI, etc.). A randomly generated value will never authenticate with any provider, leaving the service non-functional out of the box. It should be left empty, consistent with how other AI templates in this repo handle user-supplied provider keys.
  • Logo format: PNG is used instead of the SVG format recommended by AGENTS.md — minor/optional improvement.

Confidence Score: 4/5

Two P1 issues must be resolved before merging: the accidental Strapi deletion from meta.json and the misconfigured AI provider API key.

The docker-compose.yml is solid and follows all conventions. The two P1 issues — unintentional removal of an existing template entry and an auto-generated value for a user-supplied credential — prevent the PR from being merge-ready as-is.

meta.json (Strapi entry deletion) and blueprints/zeroclaw/template.toml (API_KEY auto-generation)

Important Files Changed
Filename Overview
blueprints/zeroclaw/docker-compose.yml Well-formed compose file: correct version, uses expose not ports, includes restart: unless-stopped, named volume, image pinned to 0.6.7. No issues.
blueprints/zeroclaw/template.toml Domain and port wiring are correct, but api_key = "${password:64}" auto-generates a random credential for the upstream AI provider key — this value will never authenticate with OpenRouter/OpenAI and will cause the service to be non-functional on first deploy.
meta.json ZeroClaw entry added correctly (id, version, logo, tags all consistent), but the existing strapi entry was accidentally removed — its blueprint folder still exists in the repo.
blueprints/zeroclaw/zeroclaw.png Logo file present and referenced correctly in meta.json; PNG instead of the preferred SVG format per AGENTS.md, but functional.

Comments Outside Diff (1)

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

    P1 Accidental Strapi entry removal

    The strapi entry has been deleted from meta.json, but its blueprint (blueprints/strapi/) is still present in the repository. This removal is unrelated to the ZeroClaw addition and appears to be unintentional — likely a merge conflict artifact or a side-effect of running the dedup/sort script after a conflict. Without this entry, Strapi will no longer appear in the template registry even though the underlying compose files are intact.

    Please restore the Strapi entry and re-run npm run process-meta to ensure the registry is sorted correctly before merging.

Reviews (1): Last reviewed commit: "feat: add/update ZeroClaw template (v0.6..." | Re-trigger Greptile

Greptile also left 2 inline comments on this PR.

(4/5) You can add custom instructions or style guidelines for the agent 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/762 **Author:** [@theonlyhennygod](https://github.com/theonlyhennygod) **Created:** 3/29/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `zeroclaw/update-v0.6.7` --- ### 📝 Commits (1) - [`6873dbc`](https://github.com/Dokploy/templates/commit/6873dbc0abe1a5404d986b900bf44f658e6b7f94) feat: add/update ZeroClaw template (v0.6.7) ### 📊 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.6.7) — a Rust-based AI personal assistant — to the Dokploy template registry. The `docker-compose.yml` is well-structured and follows all repository conventions. However, two issues need to be addressed before merging: - **Accidental Strapi removal**: The `strapi` entry was deleted from `meta.json` even though its blueprint folder (`blueprints/strapi/`) still exists. This is unrelated to the ZeroClaw addition and appears to be an accidental side-effect, likely from a merge conflict resolution or running the sort script against a dirty tree. Restoring it is required. - **AI provider key generated as random password**: `template.toml` uses `${password:64}` to auto-generate the `API_KEY`, but this variable holds the user's upstream AI provider credential (OpenRouter, OpenAI, etc.). A randomly generated value will never authenticate with any provider, leaving the service non-functional out of the box. It should be left empty, consistent with how other AI templates in this repo handle user-supplied provider keys. - **Logo format**: PNG is used instead of the SVG format recommended by AGENTS.md — minor/optional improvement. <h3>Confidence Score: 4/5</h3> Two P1 issues must be resolved before merging: the accidental Strapi deletion from meta.json and the misconfigured AI provider API key. The docker-compose.yml is solid and follows all conventions. The two P1 issues — unintentional removal of an existing template entry and an auto-generated value for a user-supplied credential — prevent the PR from being merge-ready as-is. meta.json (Strapi entry deletion) and blueprints/zeroclaw/template.toml (API_KEY auto-generation) <details><summary><h3>Important Files Changed</h3></summary> | Filename | Overview | |----------|----------| | blueprints/zeroclaw/docker-compose.yml | Well-formed compose file: correct version, uses expose not ports, includes restart: unless-stopped, named volume, image pinned to 0.6.7. No issues. | | blueprints/zeroclaw/template.toml | Domain and port wiring are correct, but api_key = "${password:64}" auto-generates a random credential for the upstream AI provider key — this value will never authenticate with OpenRouter/OpenAI and will cause the service to be non-functional on first deploy. | | meta.json | ZeroClaw entry added correctly (id, version, logo, tags all consistent), but the existing strapi entry was accidentally removed — its blueprint folder still exists in the repo. | | blueprints/zeroclaw/zeroclaw.png | Logo file present and referenced correctly in meta.json; PNG instead of the preferred SVG format per AGENTS.md, but functional. | </details> </details> <!-- greptile_failed_comments --> <details><summary><h3>Comments Outside Diff (1)</h3></summary> 1. `meta.json`, line 5952-5969 ([link](https://github.com/dokploy/templates/blob/6873dbc0abe1a5404d986b900bf44f658e6b7f94/meta.json#L5952-L5969)) <a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **Accidental Strapi entry removal** The `strapi` entry has been deleted from `meta.json`, but its blueprint (`blueprints/strapi/`) is still present in the repository. This removal is unrelated to the ZeroClaw addition and appears to be unintentional — likely a merge conflict artifact or a side-effect of running the dedup/sort script after a conflict. Without this entry, Strapi will no longer appear in the template registry even though the underlying compose files are intact. Please restore the Strapi entry and re-run `npm run process-meta` to ensure the registry is sorted correctly before merging. </details> <!-- /greptile_failed_comments --> <sub>Reviews (1): Last reviewed commit: ["feat: add/update ZeroClaw template (v0.6..."](https://github.com/dokploy/templates/commit/6873dbc0abe1a5404d986b900bf44f658e6b7f94) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=26703226)</sub> > Greptile also left **2 inline comments** on this PR. <sub>(4/5) You can add custom instructions or style guidelines for the agent [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)) <!-- /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-29 03:36:55 -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#8670
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?