This PR adds a new Construct template (v2026.5.3-beta.87), an autonomous AI assistant built in Rust, with a properly structured docker-compose.yml and template.toml. However, the meta.json change also removes the existing Strapi template entry, which is unrelated to this PR and appears unintentional.
The Strapi entry (id: "strapi") is deleted with no explanation — this would break discovery of Strapi for all Dokploy users and must be restored before merging.
Confidence Score: 3/5
Not safe to merge — unintentionally removes the Strapi template from the registry.
The new Construct blueprint itself is well-formed and follows conventions, but the accompanying meta.json change accidentally deletes an unrelated existing template (Strapi). This is a P1 regression that must be resolved before merging.
meta.json — the Strapi entry deletion needs to be reverted.
The Strapi template entry (id: "strapi") is being deleted from meta.json in this PR, but there is no mention of it in the PR description and it appears unrelated to adding the Construct template. This looks like an accidental removal — possibly caused by a merge conflict resolution or running process-meta against a stale base. Removing Strapi would break discovery of that template for all Dokploy users.
🔄 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/843
**Author:** [@kaveone](https://github.com/kaveone)
**Created:** 4/30/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `construct/update-v2026.5.3-beta.87`
---
### 📝 Commits (1)
- [`9604106`](https://github.com/Dokploy/templates/commit/96041067fa87b5ebbcb34893d287795179fe8d6e) feat: add/update Construct template (v2026.5.3-beta.87)
### 📊 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.3-beta.87), an autonomous AI assistant built in Rust, with a properly structured `docker-compose.yml` and `template.toml`. However, the `meta.json` change also **removes the existing Strapi template entry**, which is unrelated to this PR and appears unintentional.
- The Strapi entry (`id: "strapi"`) is deleted with no explanation — this would break discovery of Strapi for all Dokploy users and must be restored before merging.
<h3>Confidence Score: 3/5</h3>
Not safe to merge — unintentionally removes the Strapi template from the registry.
The new Construct blueprint itself is well-formed and follows conventions, but the accompanying meta.json change accidentally deletes an unrelated existing template (Strapi). This is a P1 regression that must be resolved before merging.
meta.json — the Strapi entry deletion needs to be reverted.
<!-- greptile_failed_comments -->
<details><summary><h3>Comments Outside Diff (1)</h3></summary>
1. `meta.json`, line 5968-5983 ([link](https://github.com/dokploy/templates/blob/96041067fa87b5ebbcb34893d287795179fe8d6e/meta.json#L5968-L5983))
<a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **Unintentional removal of Strapi template entry**
The Strapi template entry (`id: "strapi"`) is being deleted from `meta.json` in this PR, but there is no mention of it in the PR description and it appears unrelated to adding the Construct template. This looks like an accidental removal — possibly caused by a merge conflict resolution or running `process-meta` against a stale base. Removing Strapi would break discovery of that template for all Dokploy users.
</details>
<!-- /greptile_failed_comments -->
<sub>Reviews (1): Last reviewed commit: ["feat: add/update Construct template (v20..."](https://github.com/dokploy/templates/commit/96041067fa87b5ebbcb34893d287795179fe8d6e) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30281556)</sub>
> Greptile also left **1 inline comment** 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/843
Author: @kaveone
Created: 4/30/2026
Status: 🔄 Open
Base:
main← Head:construct/update-v2026.5.3-beta.87📝 Commits (1)
9604106feat: add/update Construct template (v2026.5.3-beta.87)📊 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.3-beta.87), an autonomous AI assistant built in Rust, with a properly structured
docker-compose.ymlandtemplate.toml. However, themeta.jsonchange also removes the existing Strapi template entry, which is unrelated to this PR and appears unintentional.id: "strapi") is deleted with no explanation — this would break discovery of Strapi for all Dokploy users and must be restored before merging.Confidence Score: 3/5
Not safe to merge — unintentionally removes the Strapi template from the registry.
The new Construct blueprint itself is well-formed and follows conventions, but the accompanying meta.json change accidentally deletes an unrelated existing template (Strapi). This is a P1 regression that must be resolved before merging.
meta.json — the Strapi entry deletion needs to be reverted.
Comments Outside Diff (1)
meta.json, line 5968-5983 (link)The Strapi template entry (
id: "strapi") is being deleted frommeta.jsonin this PR, but there is no mention of it in the PR description and it appears unrelated to adding the Construct template. This looks like an accidental removal — possibly caused by a merge conflict resolution or runningprocess-metaagainst a stale base. Removing Strapi would break discovery of that template for all Dokploy users.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.