[PR #846] feat: add/update Construct template (v2026.5.3-beta.90) #5150

New Issue

GiteaMirror · 2026-05-06T17:58:42-05:00

GiteaMirror commented

2026-05-06 17:58:42 -05:00

📋 Pull Request Information

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

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

📝 Commits (1)

5c54d5c feat: add/update Construct template (v2026.5.3-beta.90)

📊 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.90) and removes a duplicate Strapi entry from meta.json — the base branch had two identical Strapi objects, so the dedup is correct. The docker-compose structure follows all conventions (v3.8, expose only, restart: unless-stopped, named volume).

P1 — service won't function out of the box: the template auto-generates a random 64-char string for the LLM provider credential variable, but users must supply their own real OpenRouter (or other provider) key. Every LLM call will fail until the user discovers and manually replaces the generated value.

Confidence Score: 3/5

The P1 issue (auto-generated random key replacing a required external API credential) should be resolved before merging — the service will deploy but be non-functional by default.

One clear P1 defect: the template generates a random password for API_KEY instead of prompting the user to supply a real LLM provider key, so the service starts but cannot make any API calls. The remaining findings are P2 (logo format, provider flexibility). The Strapi removal is valid deduplication.

blueprints/construct/template.toml — the api_key variable default needs rethinking.

Comments Outside Diff (1)

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

SVG preferred over PNG for logo

Per the project's AGENTS.md contribution guide, SVG is the preferred logo format (~128×128px). A PNG logo will work functionally, but SVG scales better across different display sizes and DPIs used in the Dokploy UI.

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 2 inline comments 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/846 **Author:** [@kaveone](https://github.com/kaveone) **Created:** 4/30/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `construct/update-v2026.5.3-beta.90` --- ### 📝 Commits (1) - [`5c54d5c`](https://github.com/Dokploy/templates/commit/5c54d5c6e204a260d87835d458af59c687ee8708) feat: add/update Construct template (v2026.5.3-beta.90) ### 📊 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  <h3>Greptile Summary</h3> This PR adds the Construct AI assistant template (v2026.5.3-beta.90) and removes a duplicate Strapi entry from `meta.json` — the base branch had two identical Strapi objects, so the dedup is correct. The docker-compose structure follows all conventions (v3.8, `expose` only, `restart: unless-stopped`, named volume). - **P1 — service won't function out of the box:** the template auto-generates a random 64-char string for the LLM provider credential variable, but users must supply their own real OpenRouter (or other provider) key. Every LLM call will fail until the user discovers and manually replaces the generated value. <h3>Confidence Score: 3/5</h3> The P1 issue (auto-generated random key replacing a required external API credential) should be resolved before merging — the service will deploy but be non-functional by default. One clear P1 defect: the template generates a random password for API_KEY instead of prompting the user to supply a real LLM provider key, so the service starts but cannot make any API calls. The remaining findings are P2 (logo format, provider flexibility). The Strapi removal is valid deduplication. blueprints/construct/template.toml — the api_key variable default needs rethinking.  <details><summary><h3>Comments Outside Diff (1)</h3></summary> 1. `blueprints/construct/construct.png`, line 1 ([link](https://github.com/dokploy/templates/blob/5c54d5c6e204a260d87835d458af59c687ee8708/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 preferred over PNG for logo** Per the project's AGENTS.md contribution guide, SVG is the preferred logo format (~128×128px). A PNG logo will work functionally, but SVG scales better across different display sizes and DPIs used in the Dokploy UI. **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>  <sub>Reviews (1): Last reviewed commit: ["feat: add/update Construct template (v20..."](https://github.com/dokploy/templates/commit/5c54d5c6e204a260d87835d458af59c687ee8708) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30297731)</sub> > Greptile also left **2 inline comments** on this PR. **Context used:** - Context used - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))  --- <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:42 -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#5150