This PR adds a new Construct (KumihoIO/construct-os) blueprint template at version 2026.4.24-beta.52. The structural template files are well-formed and follow Dokploy conventions, but there is one notable metadata error and a few minor inconsistencies worth addressing before merging.
P1 — Wrong website URL:meta.json sets "website": "https://construct.com/", which is the homepage of Construct 3 (a game engine by Scirra), completely unrelated to this AI assistant. This will mislead users.
The Strapi removal visible in the diff is a deduplication artifact from running process-meta (a second copy of the Strapi entry existed); one copy remains in meta.json and the blueprint directory is intact.
Confidence Score: 3/5
Not safe to merge until the incorrect website URL pointing to a different product is corrected.
One P1 finding (wrong website link sending users to an unrelated commercial product) prevents a clean merge. P2 findings are minor style/usability items.
🔄 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/819
**Author:** [@kaveone](https://github.com/kaveone)
**Created:** 4/28/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `construct/update-v2026.4.24-beta.52`
---
### 📝 Commits (1)
- [`448b3bd`](https://github.com/Dokploy/templates/commit/448b3bd6cdee8088647059a144665917f632f550) feat: add/update Construct template (v2026.4.24-beta.52)
### 📊 Changes
**4 files changed** (+48 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` (+16 -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 (KumihoIO/construct-os) blueprint template at version `2026.4.24-beta.52`. The structural template files are well-formed and follow Dokploy conventions, but there is one notable metadata error and a few minor inconsistencies worth addressing before merging.
- **P1 — Wrong website URL:** `meta.json` sets `"website": "https://construct.com/"`, which is the homepage of *Construct 3* (a game engine by Scirra), completely unrelated to this AI assistant. This will mislead users.
- The Strapi removal visible in the diff is a deduplication artifact from running `process-meta` (a second copy of the Strapi entry existed); one copy remains in `meta.json` and the blueprint directory is intact.
<h3>Confidence Score: 3/5</h3>
Not safe to merge until the incorrect website URL pointing to a different product is corrected.
One P1 finding (wrong `website` link sending users to an unrelated commercial product) prevents a clean merge. P2 findings are minor style/usability items.
`meta.json` — incorrect `website` field; `blueprints/construct/docker-compose.yml` — mixed-case image ref and default-value env syntax.
<sub>Reviews (1): Last reviewed commit: ["feat: add/update Construct template (v20..."](https://github.com/dokploy/templates/commit/448b3bd6cdee8088647059a144665917f632f550) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=29957682)</sub>
> Greptile also left **4 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/819
Author: @kaveone
Created: 4/28/2026
Status: 🔄 Open
Base:
main← Head:construct/update-v2026.4.24-beta.52📝 Commits (1)
448b3bdfeat: add/update Construct template (v2026.4.24-beta.52)📊 Changes
4 files changed (+48 additions, -18 deletions)
View changed files
➕
blueprints/construct/construct.png(+0 -0)➕
blueprints/construct/docker-compose.yml(+16 -0)➕
blueprints/construct/template.toml(+16 -0)📝
meta.json(+16 -18)📄 Description
Summary
ghcr.io/KumihoIO/construct-os:${VERSION}Checklist
Testing
Links
Greptile Summary
This PR adds a new Construct (KumihoIO/construct-os) blueprint template at version
2026.4.24-beta.52. The structural template files are well-formed and follow Dokploy conventions, but there is one notable metadata error and a few minor inconsistencies worth addressing before merging.meta.jsonsets"website": "https://construct.com/", which is the homepage of Construct 3 (a game engine by Scirra), completely unrelated to this AI assistant. This will mislead users.process-meta(a second copy of the Strapi entry existed); one copy remains inmeta.jsonand the blueprint directory is intact.Confidence Score: 3/5
Not safe to merge until the incorrect website URL pointing to a different product is corrected.
One P1 finding (wrong
websitelink sending users to an unrelated commercial product) prevents a clean merge. P2 findings are minor style/usability items.meta.json— incorrectwebsitefield;blueprints/construct/docker-compose.yml— mixed-case image ref and default-value env syntax.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.