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 #844] [CLOSED] feat: add/update Construct template (v2026.5.3-beta.88) #10028

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

📋 Pull Request Information

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

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

📝 Commits (1)

  • 44a0532 feat: add/update Construct template (v2026.5.3-beta.88)

📊 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 (ghcr.io/kumihoio/construct-os:2026.5.3-beta.88) and incidentally removes a duplicate strapi entry from meta.json (a copy still exists at line 5935, so no data loss). The docker-compose and template.toml are structurally sound — correct version, expose instead of ports, restart: unless-stopped, named volume, and a properly scoped generated API_KEY.

Confidence Score: 4/5

Safe to merge — only P2 style suggestions found.

The template follows all structural conventions (version 3.8, no ports, restart policy, named volumes, matching service/folder name, pinned image). The only findings are a preference for SVG over PNG and a minor redundancy between the hardcoded PROVIDER in docker-compose.yml and the template.toml variable.

No files require special attention.

Comments Outside Diff (1)

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

    P2 SVG logo preferred over PNG

    Per the contribution guidelines, SVG is the preferred logo format (~128×128 px). PNG works fine but SVG scales cleanly at any resolution in the template browser. Consider providing an SVG version if one is available from the upstream project.

    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/844 **Author:** [@kaveone](https://github.com/kaveone) **Created:** 4/30/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `construct/update-v2026.5.3-beta.88` --- ### 📝 Commits (1) - [`44a0532`](https://github.com/Dokploy/templates/commit/44a053293ae1a737ef77b0e25a05859721b4d92a) feat: add/update Construct template (v2026.5.3-beta.88) ### 📊 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 (`ghcr.io/kumihoio/construct-os:2026.5.3-beta.88`) and incidentally removes a duplicate `strapi` entry from `meta.json` (a copy still exists at line 5935, so no data loss). The docker-compose and template.toml are structurally sound — correct version, `expose` instead of `ports`, `restart: unless-stopped`, named volume, and a properly scoped generated `API_KEY`. <h3>Confidence Score: 4/5</h3> Safe to merge — only P2 style suggestions found. The template follows all structural conventions (version 3.8, no ports, restart policy, named volumes, matching service/folder name, pinned image). The only findings are a preference for SVG over PNG and a minor redundancy between the hardcoded PROVIDER in docker-compose.yml and the template.toml variable. No files require special attention. <!-- greptile_failed_comments --> <details><summary><h3>Comments Outside Diff (1)</h3></summary> 1. `blueprints/construct/construct.png`, line 1 ([link](https://github.com/dokploy/templates/blob/44a053293ae1a737ef77b0e25a05859721b4d92a/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> **SVG logo preferred over PNG** Per the contribution guidelines, SVG is the preferred logo format (~128×128 px). PNG works fine but SVG scales cleanly at any resolution in the template browser. Consider providing an SVG version if one is available from the upstream project. **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/44a053293ae1a737ef77b0e25a05859721b4d92a) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30284931)</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-06-05 09:21:20 -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#10028
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?