[PR #752] feat: add Sim Studio template #2871

New Issue

GiteaMirror · 2026-04-23T03:36:59-05:00

GiteaMirror commented

2026-04-23 03:36:59 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/752
Author: @trfi
Created: 3/25/2026
Status: 🔄 Open

Base: canary ← Head: canary

📝 Commits (1)

5f1c2dc feat: add Sim Studio template

📊 Changes

4 files changed (+146 additions, -18 deletions)

View changed files

➕ blueprints/simstudio/docker-compose.yml (+96 -0)
➕ blueprints/simstudio/simstudio.svg (+1 -0)
➕ blueprints/simstudio/template.toml (+30 -0)
📝 meta.json (+19 -18)

📄 Description

What is this PR about?

New template for Sim Studio — an open-source AI workflow builder for designing, simulating, and testing multi-agent pipelines with real-time collaboration.

Checklist

Before submitting this PR, please make sure that:

I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template
I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
I have added tests that demonstrate that my correction works or that my new feature works.

N/A

Screenshots or Videos

Services included:

simstudio — main app (port 3000)
realtime — WebSocket collaboration server (port 3002)
migrations — one-shot init container (runs DB migrations)
db — pgvector/pgvector:pg17 (Postgres with vector extension)

All secrets (BETTER_AUTH_SECRET, ENCRYPTION_KEY, INTERNAL_API_SECRET, POSTGRES_PASSWORD) are auto-generated by Dokploy on deploy.

Greptile Summary

This PR adds a Sim Studio template — an open-source AI workflow builder with multi-agent support — comprising four services (simstudio, realtime, migrations, db). The overall architecture is solid: proper depends_on conditions, healthchecks, a one-shot migration container, and auto-generated secrets via template.toml. The apparent Strapi removal in meta.json is benign — it deduplicates an entry that already existed twice in the base branch.

However, two mandatory AGENTS.md conventions are violated that must be resolved before merging:

ports instead of expose: Both simstudio (3000) and realtime (3002) use ports: — AGENTS.md explicitly forbids this and requires expose: so Dokploy's networking layer handles routing.
Missing version: "3.8": The top-level Compose version declaration is absent; all blueprints are required to include it.
Unpinned :latest image tags (P2): All three ghcr.io/simstudioai/* images float on :latest, against the security guideline to pin to specific versions. The meta.json "version": "latest" should be updated to match once a tag is pinned.

Confidence Score: 2/5

Not safe to merge — two mandatory AGENTS.md conventions are violated (ports vs expose, missing version: "3.8") that will cause deployment issues on Dokploy.
The template structure and secret management are well done, but the two hard requirements from AGENTS.md (expose instead of ports, version: "3.8") are both missing. These are flagged as CRITICAL in the guide and will prevent the template from working correctly in Dokploy's networking model. Once those two fixes are applied (plus optionally pinning image versions), the PR should be ready to merge.
blueprints/simstudio/docker-compose.yml needs the ports → expose change and the version: "3.8" header added.

_{Reviews (1): Last reviewed commit: "feat: add Sim Studio template" | Re-trigger Greptile}

Greptile also left 4 inline comments on this PR.

_{(2/5) Greptile learns from your feedback when you react with thumbs up/down!}

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/752 **Author:** [@trfi](https://github.com/trfi) **Created:** 3/25/2026 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `canary` --- ### 📝 Commits (1) - [`5f1c2dc`](https://github.com/Dokploy/templates/commit/5f1c2dc186a060da95b38617e8f82350e60dcaeb) feat: add Sim Studio template ### 📊 Changes **4 files changed** (+146 additions, -18 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/simstudio/docker-compose.yml` (+96 -0) ➕ `blueprints/simstudio/simstudio.svg` (+1 -0) ➕ `blueprints/simstudio/template.toml` (+30 -0) 📝 `meta.json` (+19 -18) </details> ### 📄 Description ## What is this PR about? New template for [Sim Studio](https://simstudio.ai/) — an open-source AI workflow builder for designing, simulating, and testing multi-agent pipelines with real-time collaboration. ## Checklist Before submitting this PR, please make sure that: - [x] I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template - [x] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong. - [x] I have added tests that demonstrate that my correction works or that my new feature works. ## Issues related (if applicable) N/A ## Screenshots or Videos <img width="1478" height="1308" alt="image" src="https://github.com/user-attachments/assets/33eb4ce5-a1ff-4fc9-a024-4b50a67f2bbd" /> **Services included:** - `simstudio` — main app (port 3000) - `realtime` — WebSocket collaboration server (port 3002) - `migrations` — one-shot init container (runs DB migrations) - `db` — pgvector/pgvector:pg17 (Postgres with vector extension) All secrets (`BETTER_AUTH_SECRET`, `ENCRYPTION_KEY`, `INTERNAL_API_SECRET`, `POSTGRES_PASSWORD`) are auto-generated by Dokploy on deploy.  <h3>Greptile Summary</h3> This PR adds a Sim Studio template — an open-source AI workflow builder with multi-agent support — comprising four services (`simstudio`, `realtime`, `migrations`, `db`). The overall architecture is solid: proper `depends_on` conditions, healthchecks, a one-shot migration container, and auto-generated secrets via `template.toml`. The apparent Strapi removal in `meta.json` is benign — it deduplicates an entry that already existed twice in the base branch. However, two **mandatory AGENTS.md conventions** are violated that must be resolved before merging: - **`ports` instead of `expose`**: Both `simstudio` (3000) and `realtime` (3002) use `ports:` — AGENTS.md explicitly forbids this and requires `expose:` so Dokploy's networking layer handles routing. - **Missing `version: "3.8"`**: The top-level Compose version declaration is absent; all blueprints are required to include it. - **Unpinned `:latest` image tags** (P2): All three `ghcr.io/simstudioai/*` images float on `:latest`, against the security guideline to pin to specific versions. The `meta.json` `"version": "latest"` should be updated to match once a tag is pinned. <h3>Confidence Score: 2/5</h3> - Not safe to merge — two mandatory AGENTS.md conventions are violated (`ports` vs `expose`, missing `version: "3.8"`) that will cause deployment issues on Dokploy. - The template structure and secret management are well done, but the two hard requirements from AGENTS.md (`expose` instead of `ports`, `version: "3.8"`) are both missing. These are flagged as CRITICAL in the guide and will prevent the template from working correctly in Dokploy's networking model. Once those two fixes are applied (plus optionally pinning image versions), the PR should be ready to merge. - `blueprints/simstudio/docker-compose.yml` needs the `ports` → `expose` change and the `version: "3.8"` header added. <sub>Reviews (1): Last reviewed commit: ["feat: add Sim Studio template"](https://github.com/dokploy/templates/commit/3c4ffef8ff17a40c4ea1c97a7562c0e2fc480fe8) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=26268048)</sub> > Greptile also left **4 inline comments** on this PR. <sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub> **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-23 03:36:59 -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#2871