[PR #823] [CLOSED] feat: add/update Construct template (v2026.4.28) #6321

Closed
opened 2026-05-16 04:50:16 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/823
Author: @kaveone
Created: 4/28/2026
Status: Closed

Base: mainHead: construct/update-v2026.4.28


📝 Commits (1)

  • 67e9c52 feat: add/update Construct template (v2026.4.28)

📊 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 blueprint (a Rust-based AI assistant) with docker-compose.yml, template.toml, logo, and a meta.json entry. The template itself is well-structured and follows Dokploy conventions (correct version: "3.8", expose not ports, named volume, restart: unless-stopped, pinned image tag, proper template.toml variable/domain setup).

  • P1 — unintended deletion: The strapi entry is removed from meta.json even though blueprints/strapi/ still exists on main. The Strapi blueprint is completely unrelated to this PR and must be restored before merging.

Confidence Score: 3/5

Not safe to merge — the Strapi template is accidentally deleted from meta.json.

A single P1 finding (deletion of an unrelated, existing template entry) prevents a clean merge. The Construct template itself looks correct, but the side-effect on Strapi needs to be fixed first.

meta.json — Strapi entry must be restored.

Comments Outside Diff (2)

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

    P1 Accidental Strapi deletion

    This PR removes the entire strapi entry from meta.json even though the blueprints/strapi/ directory (with docker-compose.yml, template.toml, and strapi.svg) still exists on main. Strapi is an unrelated, popular headless CMS template that should not be deleted here. This looks like an unintended side-effect of running dedupe-and-sort-meta.js or a manual edit conflict — the entry needs to be restored before merging.

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

    P2 PNG logo — SVG preferred

    The contribution guide (AGENTS.md) recommends SVG format (~128×128 px) for blueprint logos. A PNG will work but may not scale as cleanly in the UI. If an SVG version is available upstream, please use it instead.

    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.


🔄 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/823 **Author:** [@kaveone](https://github.com/kaveone) **Created:** 4/28/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `construct/update-v2026.4.28` --- ### 📝 Commits (1) - [`67e9c52`](https://github.com/Dokploy/templates/commit/67e9c52a7c2b7378026442c4c6ed336b91c49cd1) feat: add/update Construct template (v2026.4.28) ### 📊 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** blueprint (a Rust-based AI assistant) with `docker-compose.yml`, `template.toml`, logo, and a `meta.json` entry. The template itself is well-structured and follows Dokploy conventions (correct `version: "3.8"`, `expose` not `ports`, named volume, `restart: unless-stopped`, pinned image tag, proper `template.toml` variable/domain setup). - **P1 — unintended deletion:** The `strapi` entry is removed from `meta.json` even though `blueprints/strapi/` still exists on `main`. The Strapi blueprint is completely unrelated to this PR and must be restored before merging. <h3>Confidence Score: 3/5</h3> Not safe to merge — the Strapi template is accidentally deleted from meta.json. A single P1 finding (deletion of an unrelated, existing template entry) prevents a clean merge. The Construct template itself looks correct, but the side-effect on Strapi needs to be fixed first. meta.json — Strapi entry must be restored. <!-- 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/67e9c52a7c2b7378026442c4c6ed336b91c49cd1/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> **Accidental Strapi deletion** This PR removes the entire `strapi` entry from `meta.json` even though the `blueprints/strapi/` directory (with `docker-compose.yml`, `template.toml`, and `strapi.svg`) still exists on `main`. Strapi is an unrelated, popular headless CMS template that should not be deleted here. This looks like an unintended side-effect of running `dedupe-and-sort-meta.js` or a manual edit conflict — the entry needs to be restored before merging. 2. `blueprints/construct/construct.png`, line 1 ([link](https://github.com/dokploy/templates/blob/67e9c52a7c2b7378026442c4c6ed336b91c49cd1/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** The contribution guide (`AGENTS.md`) recommends SVG format (~128×128 px) for blueprint logos. A PNG will work but may not scale as cleanly in the UI. If an SVG version is available upstream, please use it instead. **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/67e9c52a7c2b7378026442c4c6ed336b91c49cd1) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=29972245)</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>
GiteaMirror added the pull-request label 2026-05-16 04:50:16 -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#6321