mirror of
https://github.com/Dokploy/templates.git
synced 2026-05-07 09:10:20 -05:00
[PR #836] feat: add/update Construct template (v2026.5.3-beta.77) #4304
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/836
Author: @kaveone
Created: 4/29/2026
Status: 🔄 Open
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.