This PR adds a new Construct blueprint (v2026.5.3) — a Rust-based AI assistant — with a valid docker-compose.yml, template.toml, and logo, and registers it in meta.json. However, the meta.json diff also removes the existing Strapi entry from the registry, even though all Strapi blueprint files remain on disk; this appears to be an accidental side-effect of the meta processing step and must be restored before merging.
Confidence Score: 3/5
Not safe to merge — the Strapi template is unintentionally deleted from the registry.
One P1 finding: the Strapi entry is removed from meta.json, making it invisible in the Dokploy template registry for all users. This is a real regression introduced as a side-effect of this PR and must be fixed before merging. The Construct blueprint itself is otherwise well-formed.
meta.json — the Strapi entry deletion must be reverted.
The Strapi entry is deleted from meta.json in this PR, even though its blueprint files (blueprints/strapi/docker-compose.yml, strapi.svg, template.toml) still exist on disk. Removing it from the registry will make Strapi invisible to all Dokploy users, which is an unintended side effect of a PR that is supposed to only add the Construct template. This is likely a result of an incomplete or incorrect node dedupe-and-sort-meta.js run. The Strapi entry should be restored 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/847
**Author:** [@kaveone](https://github.com/kaveone)
**Created:** 4/30/2026
**Status:** ❌ Closed
**Base:** `main` ← **Head:** `construct/update-v2026.5.3`
---
### 📝 Commits (1)
- [`ac0e285`](https://github.com/Dokploy/templates/commit/ac0e28569b8f35db367de9988109229ac7173d9f) feat: add/update Construct template (v2026.5.3)
### 📊 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 blueprint (v2026.5.3) — a Rust-based AI assistant — with a valid `docker-compose.yml`, `template.toml`, and logo, and registers it in `meta.json`. However, the `meta.json` diff also **removes the existing Strapi entry** from the registry, even though all Strapi blueprint files remain on disk; this appears to be an accidental side-effect of the meta processing step and must be restored before merging.
<h3>Confidence Score: 3/5</h3>
Not safe to merge — the Strapi template is unintentionally deleted from the registry.
One P1 finding: the Strapi entry is removed from meta.json, making it invisible in the Dokploy template registry for all users. This is a real regression introduced as a side-effect of this PR and must be fixed before merging. The Construct blueprint itself is otherwise well-formed.
meta.json — the Strapi entry deletion must be reverted.
<!-- greptile_failed_comments -->
<details><summary><h3>Comments Outside Diff (1)</h3></summary>
1. `meta.json`, line 5968-5991 ([link](https://github.com/dokploy/templates/blob/ac0e28569b8f35db367de9988109229ac7173d9f/meta.json#L5968-L5991))
<a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **Strapi template unintentionally removed**
The Strapi entry is deleted from `meta.json` in this PR, even though its blueprint files (`blueprints/strapi/docker-compose.yml`, `strapi.svg`, `template.toml`) still exist on disk. Removing it from the registry will make Strapi invisible to all Dokploy users, which is an unintended side effect of a PR that is supposed to only add the Construct template. This is likely a result of an incomplete or incorrect `node dedupe-and-sort-meta.js` run. The Strapi entry should be restored before merging.
</details>
<!-- /greptile_failed_comments -->
<sub>Reviews (1): Last reviewed commit: ["feat: add/update Construct template (v20..."](https://github.com/dokploy/templates/commit/ac0e28569b8f35db367de9988109229ac7173d9f) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30298492)</sub>
> Greptile also left **2 inline comments** on this PR.
**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>
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/847
Author: @kaveone
Created: 4/30/2026
Status: ❌ Closed
Base:
main← Head:construct/update-v2026.5.3📝 Commits (1)
ac0e285feat: add/update Construct template (v2026.5.3)📊 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 blueprint (v2026.5.3) — a Rust-based AI assistant — with a valid
docker-compose.yml,template.toml, and logo, and registers it inmeta.json. However, themeta.jsondiff also removes the existing Strapi entry from the registry, even though all Strapi blueprint files remain on disk; this appears to be an accidental side-effect of the meta processing step and must be restored before merging.Confidence Score: 3/5
Not safe to merge — the Strapi template is unintentionally deleted from the registry.
One P1 finding: the Strapi entry is removed from meta.json, making it invisible in the Dokploy template registry for all users. This is a real regression introduced as a side-effect of this PR and must be fixed before merging. The Construct blueprint itself is otherwise well-formed.
meta.json — the Strapi entry deletion must be reverted.
Comments Outside Diff (1)
meta.json, line 5968-5991 (link)The Strapi entry is deleted from
meta.jsonin this PR, even though its blueprint files (blueprints/strapi/docker-compose.yml,strapi.svg,template.toml) still exist on disk. Removing it from the registry will make Strapi invisible to all Dokploy users, which is an unintended side effect of a PR that is supposed to only add the Construct template. This is likely a result of an incomplete or incorrectnode dedupe-and-sort-meta.jsrun. The Strapi entry should be restored before merging.Reviews (1): Last reviewed commit: "feat: add/update Construct template (v20..." | Re-trigger Greptile
Context used:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
[PR #847] feat: add/update Construct template (v2026.5.3)to [PR #847] [CLOSED] feat: add/update Construct template (v2026.5.3)