github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-07-13 16:16:15 -05:00
Code Issues 2.9k Packages Projects Releases Wiki Activity

[PR #834] [CLOSED] feat: add/update Construct template (v2026.5.2) #14256

New Issue
Closed
opened 2026-06-17 06:26:09 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-06-17 06:26:09 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/834
Author: @kaveone
Created: 4/29/2026
Status: ❌ Closed

Base: main ← Head: construct/update-v2026.5.2

📝 Commits (1)

  • e212dbd feat: add/update Construct template (v2026.5.2)

📊 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

  • 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

  • Read README.md suggestions
  • Tested template in personal Dokploy instance
  • Confirmed all requirements met

Testing

  • Deployed via Compose service import
  • Service starts and gateway is accessible on port 42617
  • Health check passes

Links

Greptile Summary

This PR adds a new Construct template (v2026.5.2) — a Rust-based AI personal assistant. The blueprint files are well-formed and follow all Docker Compose and template conventions. However, the meta.json diff also removes the existing strapi entry, which appears unintentional and would silently break Strapi template availability for all users of this repository.

Confidence Score: 3/5

Not safe to merge — the accidental deletion of the Strapi template entry must be restored before merging.

One P1 finding: the strapi template is silently deleted from meta.json. The Construct-specific files are clean and correctly structured, but the collateral damage to an existing template keeps this below the P1 ceiling of 4/5.

meta.json — the Strapi entry deletion needs to be reverted.

Comments Outside Diff (1)

  1. meta.json, line 5968-5984 (link)

    P1 Unrelated Strapi template deletion

    This PR removes the existing strapi entry from meta.json, but the PR description only mentions adding the Construct template. The deletion appears to be an accidental side-effect — likely from a manual edit or an incorrectly resolved merge conflict. Removing a working template from the registry would break any existing Dokploy user who tries to deploy Strapi via this template repository.

Reviews (1): Last reviewed commit: "feat: add/update Construct template (v20..." | Re-trigger Greptile

Context used:

  • Context used - AGENTS.md (source)

🔄 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/834 **Author:** [@kaveone](https://github.com/kaveone) **Created:** 4/29/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `construct/update-v2026.5.2` --- ### 📝 Commits (1) - [`e212dbd`](https://github.com/Dokploy/templates/commit/e212dbdca77e9e9a27a76ef76862e7f7f78e45ac) feat: add/update Construct template (v2026.5.2) ### 📊 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.2) — a Rust-based AI personal assistant. The blueprint files are well-formed and follow all Docker Compose and template conventions. However, the `meta.json` diff also **removes the existing `strapi` entry**, which appears unintentional and would silently break Strapi template availability for all users of this repository. <h3>Confidence Score: 3/5</h3> Not safe to merge — the accidental deletion of the Strapi template entry must be restored before merging. One P1 finding: the `strapi` template is silently deleted from `meta.json`. The Construct-specific files are clean and correctly structured, but the collateral damage to an existing template keeps this below the P1 ceiling of 4/5. `meta.json` — the Strapi entry deletion needs to be reverted. <!-- 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/e212dbdca77e9e9a27a76ef76862e7f7f78e45ac/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> **Unrelated Strapi template deletion** This PR removes the existing `strapi` entry from `meta.json`, but the PR description only mentions adding the Construct template. The deletion appears to be an accidental side-effect — likely from a manual edit or an incorrectly resolved merge conflict. Removing a working template from the registry would break any existing Dokploy user who tries to deploy Strapi via this template repository. </details> <!-- /greptile_failed_comments --> <sub>Reviews (1): Last reviewed commit: ["feat: add/update Construct template (v20..."](https://github.com/dokploy/templates/commit/e212dbdca77e9e9a27a76ef76862e7f7f78e45ac) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30127258)</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>
GiteaMirror added the pull-request label 2026-06-17 06:26:09 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#14256
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?