This PR adds a new Construct template (v2026.5.3-beta.77) — a Rust-based autonomous AI assistant — with a properly structured docker-compose.yml, template.toml, and logo. The blueprint itself follows Dokploy conventions well (correct version, expose instead of ports, named volume, auto-generated API_KEY).
P1: The PR unintentionally removes the existing strapi entry from meta.json. The Strapi blueprint files are untouched, so this appears to be a stale-branch or rebase artifact that would silently break the Strapi template for all users.
Confidence Score: 3/5
Not safe to merge until the accidental Strapi entry removal is reverted.
A P1 finding (unintended deletion of the Strapi meta.json entry) caps the score at 4; the deletion affects an existing, unrelated template with no justification, pulling the score down to 3.
meta.json — the Strapi block deletion must be reverted before merging.
This PR removes the existing strapi entry from meta.json but the Strapi blueprint files (blueprints/strapi/) are not removed and the PR description makes no mention of this change. This appears to be an accidental deletion — likely caused by a stale branch or rebase conflict. Removing the Strapi entry will break the Strapi template for all users of this template registry without any justification.
🔄 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/836
**Author:** [@kaveone](https://github.com/kaveone)
**Created:** 4/29/2026
**Status:** ❌ Closed
**Base:** `main` ← **Head:** `construct/update-v2026.5.3-beta.77`
---
### 📝 Commits (1)
- [`a4924db`](https://github.com/Dokploy/templates/commit/a4924db13d131c12be0c4d8d52b23f0e853d7ad8) feat: add/update Construct template (v2026.5.3-beta.77)
### 📊 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.77) — a Rust-based autonomous AI assistant — with a properly structured `docker-compose.yml`, `template.toml`, and logo. The blueprint itself follows Dokploy conventions well (correct version, `expose` instead of `ports`, named volume, auto-generated `API_KEY`).
- **P1**: The PR unintentionally removes the existing `strapi` entry from `meta.json`. The Strapi blueprint files are untouched, so this appears to be a stale-branch or rebase artifact that would silently break the Strapi template for all users.
<h3>Confidence Score: 3/5</h3>
Not safe to merge until the accidental Strapi entry removal is reverted.
A P1 finding (unintended deletion of the Strapi meta.json entry) caps the score at 4; the deletion affects an existing, unrelated template with no justification, pulling the score down to 3.
`meta.json` — the Strapi block deletion must be reverted before merging.
<!-- greptile_failed_comments -->
<details><summary><h3>Comments Outside Diff (1)</h3></summary>
1. `meta.json`, line 5968-5984 ([link](https://github.com/dokploy/templates/blob/a4924db13d131c12be0c4d8d52b23f0e853d7ad8/meta.json#L5968-L5984))
<a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **Unrelated removal of Strapi entry**
This PR removes the existing `strapi` entry from `meta.json` but the Strapi blueprint files (`blueprints/strapi/`) are not removed and the PR description makes no mention of this change. This appears to be an accidental deletion — likely caused by a stale branch or rebase conflict. Removing the Strapi entry will break the Strapi template for all users of this template registry without any justification.
</details>
<!-- /greptile_failed_comments -->
<sub>Reviews (1): Last reviewed commit: ["feat: add/update Construct template (v20..."](https://github.com/dokploy/templates/commit/a4924db13d131c12be0c4d8d52b23f0e853d7ad8) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30148030)</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/836
Author: @kaveone
Created: 4/29/2026
Status: ❌ Closed
Base:
main← Head:construct/update-v2026.5.3-beta.77📝 Commits (1)
a4924dbfeat: add/update Construct template (v2026.5.3-beta.77)📊 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.77) — a Rust-based autonomous AI assistant — with a properly structured
docker-compose.yml,template.toml, and logo. The blueprint itself follows Dokploy conventions well (correct version,exposeinstead ofports, named volume, auto-generatedAPI_KEY).strapientry frommeta.json. The Strapi blueprint files are untouched, so this appears to be a stale-branch or rebase artifact that would silently break the Strapi template for all users.Confidence Score: 3/5
Not safe to merge until the accidental Strapi entry removal is reverted.
A P1 finding (unintended deletion of the Strapi meta.json entry) caps the score at 4; the deletion affects an existing, unrelated template with no justification, pulling the score down to 3.
meta.json— the Strapi block deletion must be reverted before merging.Comments Outside Diff (1)
meta.json, line 5968-5984 (link)This PR removes the existing
strapientry frommeta.jsonbut the Strapi blueprint files (blueprints/strapi/) are not removed and the PR description makes no mention of this change. This appears to be an accidental deletion — likely caused by a stale branch or rebase conflict. Removing the Strapi entry will break the Strapi template for all users of this template registry without any justification.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 #836] feat: add/update Construct template (v2026.5.3-beta.77)to [PR #836] [CLOSED] feat: add/update Construct template (v2026.5.3-beta.77)