This PR adds a new Construct template (v2026.5.1-beta.69) — a Rust-based autonomous AI assistant — with a valid docker-compose.yml, template.toml, and PNG logo. The blueprint itself follows conventions correctly (version pinned, expose not ports, named volume, service name matches folder). However, the PR also inadvertently removes the existing strapi entry from meta.json while leaving blueprints/strapi/ intact, which is a meaningful regression that should be addressed before merging.
The strapi meta.json entry is deleted but blueprints/strapi/ still exists — this orphans the files and removes Strapi from the template catalog without a coordinated cleanup.
Confidence Score: 3/5
Not safe to merge as-is — the unintentional removal of the Strapi registry entry must be reverted.
A P1 is present: the Strapi template entry is deleted from meta.json while its blueprint files remain, silently breaking that template's discoverability. Two P2s (PNG logo, provider variable UX) do not affect the score ceiling but reinforce that minor cleanup is still needed.
meta.json — verify the Strapi deletion is reverted and only the Construct entry is added.
The strapi entry is deleted from meta.json in this PR, but blueprints/strapi/ (docker-compose, template.toml, SVG logo) still exists on disk. Removing only the registry entry makes Strapi invisible in the template catalog without removing the blueprint files. This appears to be an accidental edit — likely a merge-conflict resolution that went wrong — and should be reverted unless Strapi removal is intentional and handled in a separate PR.
AGENTS.md states "SVG preferred, ~128x128px" for logo files. A PNG works technically, but SVGs scale losslessly at any display size. Consider converting to SVG before merging.
🔄 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/831
**Author:** [@kaveone](https://github.com/kaveone)
**Created:** 4/29/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `construct/update-v2026.5.1-beta.69`
---
### 📝 Commits (1)
- [`a0089a1`](https://github.com/Dokploy/templates/commit/a0089a16033e7d027105e849cb0904e0bc52b116) feat: add/update Construct template (v2026.5.1-beta.69)
### 📊 Changes
**4 files changed** (+49 additions, -18 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/construct/construct.png` (+0 -0)
➕ `blueprints/construct/docker-compose.yml` (+16 -0)
➕ `blueprints/construct/template.toml` (+17 -0)
📝 `meta.json` (+16 -18)
</details>
### 📄 Description
## Summary
- Adds/updates Construct template to v${VERSION}
- Image: `ghcr.io/kumihoio/construct-os:${VERSION}`
- Construct 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/KumihoIO/construct-os
- https://github.com/orgs/KumihoIO/packages/container/package/construct
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR adds a new Construct template (v2026.5.1-beta.69) — a Rust-based autonomous AI assistant — with a valid `docker-compose.yml`, `template.toml`, and PNG logo. The blueprint itself follows conventions correctly (version pinned, `expose` not `ports`, named volume, service name matches folder). However, the PR also inadvertently removes the existing `strapi` entry from `meta.json` while leaving `blueprints/strapi/` intact, which is a meaningful regression that should be addressed before merging.
- The `strapi` meta.json entry is deleted but `blueprints/strapi/` still exists — this orphans the files and removes Strapi from the template catalog without a coordinated cleanup.
<h3>Confidence Score: 3/5</h3>
Not safe to merge as-is — the unintentional removal of the Strapi registry entry must be reverted.
A P1 is present: the Strapi template entry is deleted from meta.json while its blueprint files remain, silently breaking that template's discoverability. Two P2s (PNG logo, provider variable UX) do not affect the score ceiling but reinforce that minor cleanup is still needed.
meta.json — verify the Strapi deletion is reverted and only the Construct entry is added.
<!-- greptile_failed_comments -->
<details><summary><h3>Comments Outside Diff (2)</h3></summary>
1. `meta.json`, line 5968-5987 ([link](https://github.com/dokploy/templates/blob/a0089a16033e7d027105e849cb0904e0bc52b116/meta.json#L5968-L5987))
<a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **Unrelated Strapi entry removed**
The `strapi` entry is deleted from `meta.json` in this PR, but `blueprints/strapi/` (docker-compose, template.toml, SVG logo) still exists on disk. Removing only the registry entry makes Strapi invisible in the template catalog without removing the blueprint files. This appears to be an accidental edit — likely a merge-conflict resolution that went wrong — and should be reverted unless Strapi removal is intentional and handled in a separate PR.
2. `blueprints/construct/construct.png`, line 1 ([link](https://github.com/dokploy/templates/blob/a0089a16033e7d027105e849cb0904e0bc52b116/blueprints/construct/construct.png#L1))
<a href="#"><img alt="P2" src="https://greptile-static-assets.s3.amazonaws.com/badges/p2.svg?v=7" align="top"></a> **Logo format: PNG instead of preferred SVG**
`AGENTS.md` states "SVG preferred, ~128x128px" for logo files. A PNG works technically, but SVGs scale losslessly at any display size. Consider converting to SVG before merging.
**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>
<!-- /greptile_failed_comments -->
<sub>Reviews (1): Last reviewed commit: ["feat: add/update Construct template (v20..."](https://github.com/dokploy/templates/commit/a0089a16033e7d027105e849cb0904e0bc52b116) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30115704)</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>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/831
Author: @kaveone
Created: 4/29/2026
Status: 🔄 Open
Base:
main← Head:construct/update-v2026.5.1-beta.69📝 Commits (1)
a0089a1feat: add/update Construct template (v2026.5.1-beta.69)📊 Changes
4 files changed (+49 additions, -18 deletions)
View changed files
➕
blueprints/construct/construct.png(+0 -0)➕
blueprints/construct/docker-compose.yml(+16 -0)➕
blueprints/construct/template.toml(+17 -0)📝
meta.json(+16 -18)📄 Description
Summary
ghcr.io/kumihoio/construct-os:${VERSION}Checklist
Testing
Links
Greptile Summary
This PR adds a new Construct template (v2026.5.1-beta.69) — a Rust-based autonomous AI assistant — with a valid
docker-compose.yml,template.toml, and PNG logo. The blueprint itself follows conventions correctly (version pinned,exposenotports, named volume, service name matches folder). However, the PR also inadvertently removes the existingstrapientry frommeta.jsonwhile leavingblueprints/strapi/intact, which is a meaningful regression that should be addressed before merging.strapimeta.json entry is deleted butblueprints/strapi/still exists — this orphans the files and removes Strapi from the template catalog without a coordinated cleanup.Confidence Score: 3/5
Not safe to merge as-is — the unintentional removal of the Strapi registry entry must be reverted.
A P1 is present: the Strapi template entry is deleted from meta.json while its blueprint files remain, silently breaking that template's discoverability. Two P2s (PNG logo, provider variable UX) do not affect the score ceiling but reinforce that minor cleanup is still needed.
meta.json — verify the Strapi deletion is reverted and only the Construct entry is added.
Comments Outside Diff (2)
meta.json, line 5968-5987 (link)The
strapientry is deleted frommeta.jsonin this PR, butblueprints/strapi/(docker-compose, template.toml, SVG logo) still exists on disk. Removing only the registry entry makes Strapi invisible in the template catalog without removing the blueprint files. This appears to be an accidental edit — likely a merge-conflict resolution that went wrong — and should be reverted unless Strapi removal is intentional and handled in a separate PR.blueprints/construct/construct.png, line 1 (link)AGENTS.mdstates "SVG preferred, ~128x128px" for logo files. A PNG works technically, but SVGs scale losslessly at any display size. Consider converting to SVG before merging.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 Construct template (v20..." | Re-trigger Greptile
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.