[PR #837] [CLOSED] feat: add/update Construct template (v2026.5.3-beta.79) #10021

New Issue

GiteaMirror · 2026-06-05T09:20:34-05:00

GiteaMirror commented

2026-06-05 09:20:34 -05:00

📋 Pull Request Information

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

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

📝 Commits (1)

f99a3fa feat: add/update Construct template (v2026.5.3-beta.79)

📊 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 AI assistant template (v2026.5.3-beta.79) to the blueprint registry. The template structure is mostly correct — it follows Dokploy conventions (no ports, correct version, named volumes, service matches folder name) — but two issues need attention before merging:

The api_key variable in template.toml is initialized with a randomly generated string, but this field must be the user's actual upstream AI provider credential (e.g., OpenRouter key). Deploying with the auto-generated value means the service will fail to authenticate with any AI backend.
The Strapi entry is silently removed from meta.json while its blueprint files (blueprints/strapi/) remain in the repository, with no explanation in the PR description.

Confidence Score: 3/5

Not safe to merge as-is: deployments will fail due to the auto-generated API key issue, and an unrelated template is being silently removed.

Two P1 findings: the auto-generated credential guarantees a non-functional deployment, and the unexplained Strapi removal from meta.json (while blueprint files remain) suggests an unintentional side effect in this PR.

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

Comments Outside Diff (1)

meta.json, line 5968-5983 (link)

Unrelated Strapi entry removal

This PR removes the strapi entry from meta.json entirely, but the blueprint files (blueprints/strapi/docker-compose.yml, template.toml, strapi.svg) still exist in the repository. This effectively hides a working template from the registry with no explanation in the PR description. If Strapi is intentionally being deprecated, the PR should also remove the blueprint files and explain the rationale; otherwise this removal appears accidental.

_{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/837 **Author:** [@kaveone](https://github.com/kaveone) **Created:** 4/29/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `construct/update-v2026.5.3-beta.79` --- ### 📝 Commits (1) - [`f99a3fa`](https://github.com/Dokploy/templates/commit/f99a3fa87291b4ce2927854d580eae6d74803fe3) feat: add/update Construct template (v2026.5.3-beta.79) ### 📊 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 AI assistant template (v2026.5.3-beta.79) to the blueprint registry. The template structure is mostly correct — it follows Dokploy conventions (no `ports`, correct `version`, named volumes, service matches folder name) — but two issues need attention before merging: - The `api_key` variable in `template.toml` is initialized with a randomly generated string, but this field must be the user's actual upstream AI provider credential (e.g., OpenRouter key). Deploying with the auto-generated value means the service will fail to authenticate with any AI backend. - The Strapi entry is silently removed from `meta.json` while its blueprint files (`blueprints/strapi/`) remain in the repository, with no explanation in the PR description. <h3>Confidence Score: 3/5</h3> Not safe to merge as-is: deployments will fail due to the auto-generated API key issue, and an unrelated template is being silently removed. Two P1 findings: the auto-generated credential guarantees a non-functional deployment, and the unexplained Strapi removal from meta.json (while blueprint files remain) suggests an unintentional side effect in this PR. `blueprints/construct/template.toml` (api_key variable) and `meta.json` (Strapi removal).  <details><summary><h3>Comments Outside Diff (1)</h3></summary> 1. `meta.json`, line 5968-5983 ([link](https://github.com/dokploy/templates/blob/f99a3fa87291b4ce2927854d580eae6d74803fe3/meta.json#L5968-L5983)) <a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **Unrelated Strapi entry removal** This PR removes the `strapi` entry from `meta.json` entirely, but the blueprint files (`blueprints/strapi/docker-compose.yml`, `template.toml`, `strapi.svg`) still exist in the repository. This effectively hides a working template from the registry with no explanation in the PR description. If Strapi is intentionally being deprecated, the PR should also remove the blueprint files and explain the rationale; otherwise this removal appears accidental. </details>  <sub>Reviews (1): Last reviewed commit: ["feat: add/update Construct template (v20..."](https://github.com/dokploy/templates/commit/f99a3fa87291b4ce2927854d580eae6d74803fe3) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30180045)</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-06-05 09:20:34 -05:00

GiteaMirror closed this issue

2026-06-05 09:20:35 -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#10021