[PR #650] feat: add SimAiStudio template with PostgreSQL and realtime support #4982

New Issue

GiteaMirror · 2026-05-06T17:47:09-05:00

GiteaMirror commented

2026-05-06 17:47:09 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/650
Author: @Harikrishnan1367709
Created: 1/13/2026
Status: 🔄 Open

Base: canary ← Head: Add-SimAi-Template

📝 Commits (1)

3fd8265 feat: add SimAiStudio template with PostgreSQL and realtime support

📊 Changes

4 files changed (+152 additions, -0 deletions)

View changed files

➕ blueprints/simstudio/docker-compose.yml (+92 -0)
➕ blueprints/simstudio/sim.png (+0 -0)
➕ blueprints/simstudio/template.toml (+41 -0)
📝 meta.json (+19 -0)

📄 Description

📦 Added SimAiStudio Template

Open-source AI agent workflow platform for building intelligent automation workflows.

Services:

Next.js app (port 3000)
Realtime server (port 3002)
PostgreSQL 17 + pgvector
Automated migrations

Key Features:

✅ Dual-domain setup (main app + WebSocket subdomain)
✅ HTTPS/WSS support
✅ Health checks for all services
✅ Persistent storage

Files: docker-compose.yml, template.toml, sim.png, meta.json

Greptile Summary

Adds a new SimAiStudio template for deploying an AI agent workflow platform via Dokploy. The template includes four services: the main Next.js app, a WebSocket realtime server, a PostgreSQL database with pgvector, and a one-shot migration runner.

Template structure is correct: follows Dokploy conventions with expose (no ports), no container_name or networks, proper health checks, and volume persistence
Dual-domain setup: configures a main domain and a ws. subdomain for the realtime WebSocket server
Secret management: template.toml properly generates secrets using ${password:32}, ${base64:32}, and ${password:16} helpers
Style concern: Docker images use :latest tags rather than pinned versions, and docker-compose.yml contains weak default fallback values for secrets and admin credentials (though these are overridden by template.toml in Dokploy deployments)
meta.json entry is correctly positioned alphabetically and includes all required fields

Confidence Score: 4/5

This PR is safe to merge with minor style improvements recommended for secret defaults and image pinning.
The template is well-structured and follows Dokploy conventions correctly. The issues found are style-level concerns (unpinned image tags, weak default fallbacks) rather than functional bugs. The template.toml properly generates secure credentials, so the weak defaults in docker-compose.yml only affect standalone usage outside Dokploy. No critical logic or syntax errors found.
blueprints/simstudio/docker-compose.yml has weak default fallback values for secrets and unpinned image tags.

_{Last reviewed commit: 3fd8265}

Context used:

Context from dashboard - 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/650 **Author:** [@Harikrishnan1367709](https://github.com/Harikrishnan1367709) **Created:** 1/13/2026 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `Add-SimAi-Template` --- ### 📝 Commits (1) - [`3fd8265`](https://github.com/Dokploy/templates/commit/3fd8265c9eb8d5d93feb9499fa9cfcb163a4da18) feat: add SimAiStudio template with PostgreSQL and realtime support ### 📊 Changes **4 files changed** (+152 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/simstudio/docker-compose.yml` (+92 -0) ➕ `blueprints/simstudio/sim.png` (+0 -0) ➕ `blueprints/simstudio/template.toml` (+41 -0) 📝 `meta.json` (+19 -0) </details> ### 📄 Description ### 📦 Added SimAiStudio Template Open-source AI agent workflow platform for building intelligent automation workflows. **Services:** - Next.js app (port 3000) - Realtime server (port 3002) - PostgreSQL 17 + pgvector - Automated migrations **Key Features:** - ✅ Dual-domain setup (main app + WebSocket subdomain) - ✅ HTTPS/WSS support - ✅ Health checks for all services - ✅ Persistent storage **Files:** `docker-compose.yml`, `template.toml`, `sim.png`, `meta.json` <img width="1440" height="817" alt="Screenshot 2026-01-13 at 10 45 21 AM" src="https://github.com/user-attachments/assets/d639bd4c-de63-49fd-9eed-a44af6ccc516" />  <h3>Greptile Summary</h3> Adds a new SimAiStudio template for deploying an AI agent workflow platform via Dokploy. The template includes four services: the main Next.js app, a WebSocket realtime server, a PostgreSQL database with pgvector, and a one-shot migration runner. - **Template structure is correct**: follows Dokploy conventions with `expose` (no `ports`), no `container_name` or `networks`, proper health checks, and volume persistence - **Dual-domain setup**: configures a main domain and a `ws.` subdomain for the realtime WebSocket server - **Secret management**: `template.toml` properly generates secrets using `${password:32}`, `${base64:32}`, and `${password:16}` helpers - **Style concern**: Docker images use `:latest` tags rather than pinned versions, and `docker-compose.yml` contains weak default fallback values for secrets and admin credentials (though these are overridden by `template.toml` in Dokploy deployments) - **meta.json entry** is correctly positioned alphabetically and includes all required fields <h3>Confidence Score: 4/5</h3> - This PR is safe to merge with minor style improvements recommended for secret defaults and image pinning. - The template is well-structured and follows Dokploy conventions correctly. The issues found are style-level concerns (unpinned image tags, weak default fallbacks) rather than functional bugs. The template.toml properly generates secure credentials, so the weak defaults in docker-compose.yml only affect standalone usage outside Dokploy. No critical logic or syntax errors found. - blueprints/simstudio/docker-compose.yml has weak default fallback values for secrets and unpinned image tags. <sub>Last reviewed commit: 3fd8265</sub>  **Context used:** - Context from `dashboard` - 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:47:09 -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#4982