[PR #845] feat: add/update Construct template (v2026.5.3-beta.89) #4313

New Issue

GiteaMirror · 2026-04-30T06:52:18-05:00

GiteaMirror commented

2026-04-30 06:52:18 -05:00

📋 Pull Request Information

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

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

📝 Commits (1)

8e4036d feat: add/update Construct template (v2026.5.3-beta.89)

📊 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 a new Construct template (v2026.5.3-beta.89, a Rust-based AI personal assistant) with correct Compose conventions, but has two blocking issues before merging.

Strapi entry accidentally removed from meta.json: Blueprint files still exist under blueprints/strapi/, suggesting an unintentional regression from a merge conflict.
Provider credential misconfigured: template.toml auto-generates api_key using a random value, but this field must be the user's actual OpenRouter credential. Deploying with a randomly generated value will cause all AI requests to fail immediately.

Confidence Score: 2/5

Not safe to merge — two independent P1 issues: an accidental Strapi removal and a broken API key configuration that makes the service non-functional on deploy.

Two P1 findings: the Strapi entry removal is an unrelated regression that breaks an existing template, and the auto-generated API_KEY means Construct cannot authenticate with the AI provider and will be dead on arrival. Either alone would cap the score at 4; together they pull it to 2.

meta.json (Strapi removal) and blueprints/construct/template.toml (API_KEY variable)

_{Reviews (1): Last reviewed commit: "feat: add/update Construct template (v20..." | Re-trigger Greptile}

Greptile also left 3 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/845 **Author:** [@kaveone](https://github.com/kaveone) **Created:** 4/30/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `construct/update-v2026.5.3-beta.89` --- ### 📝 Commits (1) - [`8e4036d`](https://github.com/Dokploy/templates/commit/8e4036d43ef4c8354cb593554cecea4a4cbcad40) feat: add/update Construct template (v2026.5.3-beta.89) ### 📊 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 a new Construct template (v2026.5.3-beta.89, a Rust-based AI personal assistant) with correct Compose conventions, but has two blocking issues before merging. - **Strapi entry accidentally removed from `meta.json`**: Blueprint files still exist under `blueprints/strapi/`, suggesting an unintentional regression from a merge conflict. - **Provider credential misconfigured**: `template.toml` auto-generates `api_key` using a random value, but this field must be the user's actual OpenRouter credential. Deploying with a randomly generated value will cause all AI requests to fail immediately. <h3>Confidence Score: 2/5</h3> Not safe to merge — two independent P1 issues: an accidental Strapi removal and a broken API key configuration that makes the service non-functional on deploy. Two P1 findings: the Strapi entry removal is an unrelated regression that breaks an existing template, and the auto-generated API_KEY means Construct cannot authenticate with the AI provider and will be dead on arrival. Either alone would cap the score at 4; together they pull it to 2. meta.json (Strapi removal) and blueprints/construct/template.toml (API_KEY variable) <sub>Reviews (1): Last reviewed commit: ["feat: add/update Construct template (v20..."](https://github.com/dokploy/templates/commit/8e4036d43ef4c8354cb593554cecea4a4cbcad40) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30291133)</sub> > Greptile also left **3 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-04-30 06:52:18 -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#4313