This PR adds a new Construct AI assistant template (blueprints/construct/) with a properly structured docker-compose.yml, template.toml, and logo — the blueprint itself follows project conventions. However, the meta.json diff also removes the existing strapi template entry, even though the Strapi blueprint files remain on disk; this appears to be an accidental merge/rebase artifact and should be reverted before merging.
Confidence Score: 3/5
Not safe to merge as-is — the accidental Strapi deletion must be reverted first.
A P1 finding (unintentional removal of the Strapi registry entry) is the primary blocker; the Construct blueprint itself is well-formed with only minor P2 style notes.
meta.json — the Strapi entry deletion needs to be reverted.
This PR removes the existing strapi entry from meta.json, even though the Strapi blueprint (blueprints/strapi/docker-compose.yml, template.toml, strapi.svg) still exists on disk. Removing only the registry entry effectively hides the Strapi template from users without deleting the blueprint files — this appears accidental and should be restored. Re-running node dedupe-and-sort-meta.js after re-adding the Strapi block should place it back in the correct sort position.
The project guide recommends SVG (~128×128 px) for blueprint logos. A PNG works but may appear blurry at high DPI or when scaled. Consider replacing with an SVG version if available.
🔄 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/833
**Author:** [@kaveone](https://github.com/kaveone)
**Created:** 4/29/2026
**Status:** ❌ Closed
**Base:** `main` ← **Head:** `construct/update-v2026.5.2-beta.71`
---
### 📝 Commits (1)
- [`bbb0212`](https://github.com/Dokploy/templates/commit/bbb02128abd598f5d1cacf6ae8b8000a1b8f60a4) feat: add/update Construct template (v2026.5.2-beta.71)
### 📊 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 AI assistant template (`blueprints/construct/`) with a properly structured `docker-compose.yml`, `template.toml`, and logo — the blueprint itself follows project conventions. However, the `meta.json` diff also removes the existing `strapi` template entry, even though the Strapi blueprint files remain on disk; this appears to be an accidental merge/rebase artifact and should be reverted before merging.
<h3>Confidence Score: 3/5</h3>
Not safe to merge as-is — the accidental Strapi deletion must be reverted first.
A P1 finding (unintentional removal of the Strapi registry entry) is the primary blocker; the Construct blueprint itself is well-formed with only minor P2 style notes.
meta.json — the Strapi entry deletion needs to be reverted.
<!-- greptile_failed_comments -->
<details><summary><h3>Comments Outside Diff (2)</h3></summary>
1. `meta.json`, line 5968-5985 ([link](https://github.com/dokploy/templates/blob/bbb02128abd598f5d1cacf6ae8b8000a1b8f60a4/meta.json#L5968-L5985))
<a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **Unintentional deletion of Strapi template entry**
This PR removes the existing `strapi` entry from `meta.json`, even though the Strapi blueprint (`blueprints/strapi/docker-compose.yml`, `template.toml`, `strapi.svg`) still exists on disk. Removing only the registry entry effectively hides the Strapi template from users without deleting the blueprint files — this appears accidental and should be restored. Re-running `node dedupe-and-sort-meta.js` after re-adding the Strapi block should place it back in the correct sort position.
2. `blueprints/construct/construct.png`, line 1 ([link](https://github.com/dokploy/templates/blob/bbb02128abd598f5d1cacf6ae8b8000a1b8f60a4/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> **PNG logo — SVG preferred per project conventions**
The project guide recommends SVG (~128×128 px) for blueprint logos. A PNG works but may appear blurry at high DPI or when scaled. Consider replacing with an SVG version if available.
**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/bbb02128abd598f5d1cacf6ae8b8000a1b8f60a4) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30126937)</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/833
Author: @kaveone
Created: 4/29/2026
Status: ❌ Closed
Base:
main← Head:construct/update-v2026.5.2-beta.71📝 Commits (1)
bbb0212feat: add/update Construct template (v2026.5.2-beta.71)📊 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 AI assistant template (
blueprints/construct/) with a properly structureddocker-compose.yml,template.toml, and logo — the blueprint itself follows project conventions. However, themeta.jsondiff also removes the existingstrapitemplate entry, even though the Strapi blueprint files remain on disk; this appears to be an accidental merge/rebase artifact and should be reverted before merging.Confidence Score: 3/5
Not safe to merge as-is — the accidental Strapi deletion must be reverted first.
A P1 finding (unintentional removal of the Strapi registry entry) is the primary blocker; the Construct blueprint itself is well-formed with only minor P2 style notes.
meta.json — the Strapi entry deletion needs to be reverted.
Comments Outside Diff (2)
meta.json, line 5968-5985 (link)This PR removes the existing
strapientry frommeta.json, even though the Strapi blueprint (blueprints/strapi/docker-compose.yml,template.toml,strapi.svg) still exists on disk. Removing only the registry entry effectively hides the Strapi template from users without deleting the blueprint files — this appears accidental and should be restored. Re-runningnode dedupe-and-sort-meta.jsafter re-adding the Strapi block should place it back in the correct sort position.blueprints/construct/construct.png, line 1 (link)The project guide recommends SVG (~128×128 px) for blueprint logos. A PNG works but may appear blurry at high DPI or when scaled. Consider replacing with an SVG version if available.
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
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.