This PR adds a new Construct template (v2026.5.3-beta.76) — a Rust-based autonomous AI assistant — with a properly structured docker-compose.yml, template.toml, and meta.json entry. The template follows Dokploy conventions well (correct version pinning, expose over ports, named volumes, auto-generated API key), but contains one notable unintended change.
Strapi removed from meta.json: The blueprints/strapi/ directory and all its files still exist, but the strapi registry entry was deleted. This appears to be an accidental side-effect (merge conflict or process-meta run) and would silently hide Strapi from the template browser.
Confidence Score: 3/5
Not safe to merge until the accidentally removed Strapi entry is restored in meta.json.
A P1 defect is present: the Strapi template entry is removed from meta.json while its blueprint files remain, which would break Strapi's visibility in the template browser for all users. The new Construct template itself is well-formed.
meta.json — the Strapi entry deletion must be reverted.
The strapi entry was deleted from meta.json but its blueprint files (blueprints/strapi/docker-compose.yml, strapi.svg, template.toml) still exist. This means Strapi will silently disappear from the template browser after this PR merges. This looks like an accidental side-effect of running dedupe-and-sort-meta.js or a merge conflict — the Strapi block should be restored.
Per the contribution guidelines, SVG is the preferred logo format (~128×128px). A PNG logo may appear blurry at different display densities. Consider providing an SVG version.
🔄 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/835
**Author:** [@kaveone](https://github.com/kaveone)
**Created:** 4/29/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `construct/update-v2026.5.3-beta.76`
---
### 📝 Commits (1)
- [`74f4011`](https://github.com/Dokploy/templates/commit/74f4011cb5e136d9d3dad070e227d304dff774d9) feat: add/update Construct template (v2026.5.3-beta.76)
### 📊 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.76) — a Rust-based autonomous AI assistant — with a properly structured `docker-compose.yml`, `template.toml`, and `meta.json` entry. The template follows Dokploy conventions well (correct version pinning, `expose` over `ports`, named volumes, auto-generated API key), but contains one notable unintended change.
- **Strapi removed from `meta.json`**: The `blueprints/strapi/` directory and all its files still exist, but the `strapi` registry entry was deleted. This appears to be an accidental side-effect (merge conflict or `process-meta` run) and would silently hide Strapi from the template browser.
<h3>Confidence Score: 3/5</h3>
Not safe to merge until the accidentally removed Strapi entry is restored in meta.json.
A P1 defect is present: the Strapi template entry is removed from meta.json while its blueprint files remain, which would break Strapi's visibility in the template browser for all users. The new Construct template itself is well-formed.
meta.json — the Strapi entry deletion must be reverted.
<!-- greptile_failed_comments -->
<details><summary><h3>Comments Outside Diff (2)</h3></summary>
1. `meta.json`, line 5968-5984 ([link](https://github.com/dokploy/templates/blob/74f4011cb5e136d9d3dad070e227d304dff774d9/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> **Strapi entry accidentally removed**
The `strapi` entry was deleted from `meta.json` but its blueprint files (`blueprints/strapi/docker-compose.yml`, `strapi.svg`, `template.toml`) still exist. This means Strapi will silently disappear from the template browser after this PR merges. This looks like an accidental side-effect of running `dedupe-and-sort-meta.js` or a merge conflict — the Strapi block should be restored.
2. `blueprints/construct/construct.png`, line 1 ([link](https://github.com/dokploy/templates/blob/74f4011cb5e136d9d3dad070e227d304dff774d9/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: SVG preferred over PNG**
Per the contribution guidelines, SVG is the preferred logo format (~128×128px). A PNG logo may appear blurry at different display densities. Consider providing an SVG version.
**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/74f4011cb5e136d9d3dad070e227d304dff774d9) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30144234)</sub>
**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/835
Author: @kaveone
Created: 4/29/2026
Status: 🔄 Open
Base:
main← Head:construct/update-v2026.5.3-beta.76📝 Commits (1)
74f4011feat: add/update Construct template (v2026.5.3-beta.76)📊 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.76) — a Rust-based autonomous AI assistant — with a properly structured
docker-compose.yml,template.toml, andmeta.jsonentry. The template follows Dokploy conventions well (correct version pinning,exposeoverports, named volumes, auto-generated API key), but contains one notable unintended change.meta.json: Theblueprints/strapi/directory and all its files still exist, but thestrapiregistry entry was deleted. This appears to be an accidental side-effect (merge conflict orprocess-metarun) and would silently hide Strapi from the template browser.Confidence Score: 3/5
Not safe to merge until the accidentally removed Strapi entry is restored in meta.json.
A P1 defect is present: the Strapi template entry is removed from meta.json while its blueprint files remain, which would break Strapi's visibility in the template browser for all users. The new Construct template itself is well-formed.
meta.json — the Strapi entry deletion must be reverted.
Comments Outside Diff (2)
meta.json, line 5968-5984 (link)The
strapientry was deleted frommeta.jsonbut its blueprint files (blueprints/strapi/docker-compose.yml,strapi.svg,template.toml) still exist. This means Strapi will silently disappear from the template browser after this PR merges. This looks like an accidental side-effect of runningdedupe-and-sort-meta.jsor a merge conflict — the Strapi block should be restored.blueprints/construct/construct.png, line 1 (link)Per the contribution guidelines, SVG is the preferred logo format (~128×128px). A PNG logo may appear blurry at different display densities. Consider providing an SVG version.
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
Context used:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.