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

[PR #839] [CLOSED] feat: add/update Construct template (v2026.5.3-beta.82) #14261

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

📋 Pull Request Information

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

Base: main ← Head: construct/update-v2026.5.3-beta.82

📝 Commits (1)

  • a8950ec feat: add/update Construct template (v2026.5.3-beta.82)

📊 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 the Construct AI assistant template (v2026.5.3-beta.82) to the blueprint catalogue. The new template files are well-formed — correct Docker Compose version, expose instead of ports, named volumes, proper template.toml variable helpers — but the meta.json edit accidentally deletes the existing Strapi entry while its full blueprint (blueprints/strapi/) still exists in the repo.

  • Strapi entry removed from meta.json without removing blueprints/strapi/, making Strapi invisible in the template catalogue — this needs to be restored before merging.

Confidence Score: 3/5

Not safe to merge as-is — the accidental Strapi deletion must be reverted.

A P1 defect (removal of the Strapi meta.json entry while its blueprint files still exist) is present. Per the scoring rubric, a P1 finding caps the score at 4, and the fact that it silently breaks an existing template warrants pulling the score down to 3.

meta.json — the Strapi entry deletion starting around line 5968 needs to be reverted.

Comments Outside Diff (2)

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

    P1 Accidental Strapi entry deletion

    The Strapi template entry is being removed from meta.json, but blueprints/strapi/ still contains all its files (docker-compose.yml, template.toml, strapi.svg). Removing the meta.json entry while leaving the blueprint in place will make Strapi disappear from the Dokploy template catalogue entirely, breaking discovery and deployment for all users relying on it. This deletion appears unrelated to adding Construct and is likely an accidental edit conflict or copy-paste error during meta.json modification.

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

    P2 PNG logo instead of preferred SVG

    AGENTS.md recommends SVG format for logo files (~128×128px) since SVGs scale cleanly at all resolutions. A PNG will work but may appear pixelated in some UI contexts. Consider providing an SVG variant 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

🔄 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/839 **Author:** [@kaveone](https://github.com/kaveone) **Created:** 4/29/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `construct/update-v2026.5.3-beta.82` --- ### 📝 Commits (1) - [`a8950ec`](https://github.com/Dokploy/templates/commit/a8950ec9ccfc4492525392ed8dbf285bb901af7c) feat: add/update Construct template (v2026.5.3-beta.82) ### 📊 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 the Construct AI assistant template (v2026.5.3-beta.82) to the blueprint catalogue. The new template files are well-formed — correct Docker Compose version, `expose` instead of `ports`, named volumes, proper `template.toml` variable helpers — but the `meta.json` edit accidentally deletes the existing **Strapi** entry while its full blueprint (`blueprints/strapi/`) still exists in the repo. - **Strapi entry removed** from `meta.json` without removing `blueprints/strapi/`, making Strapi invisible in the template catalogue — this needs to be restored before merging. <h3>Confidence Score: 3/5</h3> Not safe to merge as-is — the accidental Strapi deletion must be reverted. A P1 defect (removal of the Strapi meta.json entry while its blueprint files still exist) is present. Per the scoring rubric, a P1 finding caps the score at 4, and the fact that it silently breaks an existing template warrants pulling the score down to 3. `meta.json` — the Strapi entry deletion starting around line 5968 needs to be reverted. <!-- 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/a8950ec9ccfc4492525392ed8dbf285bb901af7c/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> **Accidental Strapi entry deletion** The Strapi template entry is being removed from `meta.json`, but `blueprints/strapi/` still contains all its files (`docker-compose.yml`, `template.toml`, `strapi.svg`). Removing the `meta.json` entry while leaving the blueprint in place will make Strapi disappear from the Dokploy template catalogue entirely, breaking discovery and deployment for all users relying on it. This deletion appears unrelated to adding Construct and is likely an accidental edit conflict or copy-paste error during `meta.json` modification. 2. `blueprints/construct/construct.png`, line 1 ([link](https://github.com/dokploy/templates/blob/a8950ec9ccfc4492525392ed8dbf285bb901af7c/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 instead of preferred SVG** `AGENTS.md` recommends SVG format for logo files (~128×128px) since SVGs scale cleanly at all resolutions. A PNG will work but may appear pixelated in some UI contexts. Consider providing an SVG variant 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/a8950ec9ccfc4492525392ed8dbf285bb901af7c) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30259214)</sub> <!-- /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:35 -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#14261
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?