This PR adds a new Construct template (v2026.5.1) — a Rust-based autonomous AI assistant — with the correct blueprint structure. However, it also unintentionally removes the Strapi entry from meta.json while the Strapi blueprint files still exist in the repository, which would cause Strapi to disappear from the template registry.
The Strapi meta.json entry is deleted in this PR even though blueprints/strapi/ files are untouched — this must be restored before merging.
Confidence Score: 3/5
Not safe to merge — unintentionally removes the Strapi template registry entry while its blueprint files remain.
A P1 finding (accidental deletion of an existing template's meta.json entry) blocks a clean merge. The Construct template itself is well-structured and follows conventions.
meta.json — the Strapi entry deletion must be reverted before merging.
This PR removes the entire Strapi entry from meta.json, but the Strapi blueprint files (blueprints/strapi/docker-compose.yml, template.toml, strapi.svg) still exist in the repository. Strapi would disappear from the template registry without its files being touched. This looks like an accidental deletion — possibly a merge conflict resolution or a manual edit that went wrong before running process-meta.
🔄 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/832
**Author:** [@kaveone](https://github.com/kaveone)
**Created:** 4/29/2026
**Status:** ❌ Closed
**Base:** `main` ← **Head:** `construct/update-v2026.5.1`
---
### 📝 Commits (1)
- [`da2f3cc`](https://github.com/Dokploy/templates/commit/da2f3cca3fd69874492b92156913b0afaa1e8d9b) feat: add/update Construct template (v2026.5.1)
### 📊 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.1) — a Rust-based autonomous AI assistant — with the correct blueprint structure. However, it also **unintentionally removes the Strapi entry from `meta.json`** while the Strapi blueprint files still exist in the repository, which would cause Strapi to disappear from the template registry.
- The Strapi `meta.json` entry is deleted in this PR even though `blueprints/strapi/` files are untouched — this must be restored before merging.
<h3>Confidence Score: 3/5</h3>
Not safe to merge — unintentionally removes the Strapi template registry entry while its blueprint files remain.
A P1 finding (accidental deletion of an existing template's meta.json entry) blocks a clean merge. The Construct template itself is well-structured and follows conventions.
meta.json — the Strapi entry 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/da2f3cca3fd69874492b92156913b0afaa1e8d9b/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> **Unintended removal of Strapi entry**
This PR removes the entire Strapi entry from `meta.json`, but the Strapi blueprint files (`blueprints/strapi/docker-compose.yml`, `template.toml`, `strapi.svg`) still exist in the repository. Strapi would disappear from the template registry without its files being touched. This looks like an accidental deletion — possibly a merge conflict resolution or a manual edit that went wrong before running `process-meta`.
</details>
<!-- /greptile_failed_comments -->
<sub>Reviews (1): Last reviewed commit: ["feat: add/update Construct template (v20..."](https://github.com/dokploy/templates/commit/da2f3cca3fd69874492b92156913b0afaa1e8d9b) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30115836)</sub>
> Greptile also left **1 inline comment** on this PR.
<!-- /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/832
Author: @kaveone
Created: 4/29/2026
Status: ❌ Closed
Base:
main← Head:construct/update-v2026.5.1📝 Commits (1)
da2f3ccfeat: add/update Construct template (v2026.5.1)📊 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.1) — a Rust-based autonomous AI assistant — with the correct blueprint structure. However, it also unintentionally removes the Strapi entry from
meta.jsonwhile the Strapi blueprint files still exist in the repository, which would cause Strapi to disappear from the template registry.meta.jsonentry is deleted in this PR even thoughblueprints/strapi/files are untouched — this must be restored before merging.Confidence Score: 3/5
Not safe to merge — unintentionally removes the Strapi template registry entry while its blueprint files remain.
A P1 finding (accidental deletion of an existing template's meta.json entry) blocks a clean merge. The Construct template itself is well-structured and follows conventions.
meta.json — the Strapi entry deletion must be reverted before merging.
Comments Outside Diff (1)
meta.json, line 5968-5984 (link)This PR removes the entire Strapi entry from
meta.json, but the Strapi blueprint files (blueprints/strapi/docker-compose.yml,template.toml,strapi.svg) still exist in the repository. Strapi would disappear from the template registry without its files being touched. This looks like an accidental deletion — possibly a merge conflict resolution or a manual edit that went wrong before runningprocess-meta.Reviews (1): Last reviewed commit: "feat: add/update Construct template (v20..." | Re-trigger Greptile
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.