[PR #829] feat: add/update Construct template (v2026.4.30-beta.68) #5133

Open
opened 2026-05-06 17:58:15 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/829
Author: @kaveone
Created: 4/28/2026
Status: 🔄 Open

Base: mainHead: construct/update-v2026.4.30-beta.68


📝 Commits (1)

  • 3e8eaeb feat: add/update Construct template (v2026.4.30-beta.68)

📊 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

Greptile Summary

This PR adds a new Construct template (a Rust-based autonomous AI assistant) and correctly follows all Dokploy blueprint conventions. However, the meta.json diff also removes the existing Strapi entry — the Strapi blueprint directory is untouched, so this appears to be an unintentional merge artifact.

  • P1 — Strapi removed from meta.json: The Strapi template entry is deleted in this PR even though blueprints/strapi/ still exists; this would silently remove Strapi from the gallery. The Strapi block should be restored before merging.

Confidence Score: 3/5

Not safe to merge as-is — the Strapi entry must be restored in meta.json before merging.

The Construct template itself is well-formed, but the unintentional deletion of the Strapi meta.json entry is a P1 that would cause an existing template to disappear from the gallery.

meta.json — Strapi entry must be restored.

Comments Outside Diff (2)

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

    P1 Unintentional removal of Strapi entry

    The Strapi entry is removed from meta.json in this PR, even though the Strapi blueprint directory (blueprints/strapi/) and all its files still exist. This is almost certainly an unintentional side-effect — likely a merge conflict resolution that accidentally dropped the block. Removing this entry would cause the Strapi template to disappear from the Dokploy template gallery entirely.

  2. blueprints/construct/construct.png, line 1 (link)

    P2 PNG logo — SVG preferred

    Per the project's contribution guidelines, SVG is the preferred logo format (roughly 128×128 px). A PNG will work but degrades at different display sizes. Consider providing an SVG if one is available upstream.

    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

Greptile also left 1 inline comment on this PR.

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/829 **Author:** [@kaveone](https://github.com/kaveone) **Created:** 4/28/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `construct/update-v2026.4.30-beta.68` --- ### 📝 Commits (1) - [`3e8eaeb`](https://github.com/Dokploy/templates/commit/3e8eaebfc62ccf474d31fc2af2ca593df8c7a7d5) feat: add/update Construct template (v2026.4.30-beta.68) ### 📊 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 (a Rust-based autonomous AI assistant) and correctly follows all Dokploy blueprint conventions. However, the `meta.json` diff also removes the existing Strapi entry — the Strapi blueprint directory is untouched, so this appears to be an unintentional merge artifact. - **P1 — Strapi removed from `meta.json`:** The Strapi template entry is deleted in this PR even though `blueprints/strapi/` still exists; this would silently remove Strapi from the gallery. The Strapi block should be restored before merging. <h3>Confidence Score: 3/5</h3> Not safe to merge as-is — the Strapi entry must be restored in meta.json before merging. The Construct template itself is well-formed, but the unintentional deletion of the Strapi meta.json entry is a P1 that would cause an existing template to disappear from the gallery. meta.json — Strapi entry must be restored. <!-- 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/3e8eaebfc62ccf474d31fc2af2ca593df8c7a7d5/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> **Unintentional removal of Strapi entry** The Strapi entry is removed from `meta.json` in this PR, even though the Strapi blueprint directory (`blueprints/strapi/`) and all its files still exist. This is almost certainly an unintentional side-effect — likely a merge conflict resolution that accidentally dropped the block. Removing this entry would cause the Strapi template to disappear from the Dokploy template gallery entirely. 2. `blueprints/construct/construct.png`, line 1 ([link](https://github.com/dokploy/templates/blob/3e8eaebfc62ccf474d31fc2af2ca593df8c7a7d5/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 the project's contribution guidelines, SVG is the preferred logo format (roughly 128×128 px). A PNG will work but degrades at different display sizes. Consider providing an SVG if one is available upstream. **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/3e8eaebfc62ccf474d31fc2af2ca593df8c7a7d5) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30049618)</sub> > Greptile also left **1 inline comment** on this PR. **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-05-06 17:58:15 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#5133