[PR #799] Add Multica template #2911

New Issue

GiteaMirror · 2026-04-23T03:38:11-05:00

GiteaMirror commented

2026-04-23 03:38:11 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/799
Author: @enemyrr
Created: 4/17/2026
Status: 🔄 Open

Base: main ← Head: multica-clean

📝 Commits (1)

30d789c Add Multica template

📊 Changes

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

View changed files

➕ blueprints/multica/docker-compose.yml (+68 -0)
➕ blueprints/multica/multica.svg (+7 -0)
➕ blueprints/multica/template.toml (+40 -0)
📝 meta.json (+21 -0)

📄 Description

Summary

Adds a blueprint for Multica — an open-source managed agents platform for teams (assign tasks to AI coding agents like Claude Code, Codex, OpenClaw, etc.).

Services

postgres — pgvector/pgvector:pg17
backend — Go API + WebSocket server, port 8080 (built from https://github.com/multica-ai/multica.git#main with Dockerfile)
frontend — Next.js 16, port 3000 (built with Dockerfile.web)

Multica doesn't publish pre-built images yet, so the template builds from the remote git context — same pattern firecrawl/nuq-postgres uses.

Traefik domains

Two public domains are exposed:

${app_domain} → frontend:3000
${api_domain} → backend:8080 (needed by the multica CLI/daemon)

NEXT_PUBLIC_WS_URL is baked into the frontend build pointing at wss://${api_domain}/ws.

Out of the box, non-production environments accept verification code 888888 for any email. For production, set RESEND_API_KEY / RESEND_FROM_EMAIL.

Test plan

PR preview deploys successfully
Import template into a Dokploy instance, deploy
Open app_domain, log in with 888888
Verify backend is reachable at api_domain

Greptile Summary

Adds a new Multica blueprint — a three-service stack (postgres/pgvector, Go backend, Next.js frontend) that builds from the upstream git repo since no pre-built images are published. The template structure (dual-domain variables, [config.env] table, healthcheck on postgres) is consistent with existing multi-domain templates like typebot.

The only deviations from AGENTS.md conventions are: ports used instead of expose for both application services, and the missing version: "3.8" field at the top of docker-compose.yml. Both are minor style concerns with no impact on runtime behavior.

Confidence Score: 5/5

Safe to merge; all findings are P2 style/convention issues with no runtime impact.

All three comments are P2 — ports vs expose and the missing version field are documented conventions in AGENTS.md but have no functional effect on Dokploy deployments. No logic bugs, security issues, or data-integrity problems were found.

blueprints/multica/docker-compose.yml — minor style fixes for ports and version field

_{Reviews (1): Last reviewed commit: "Add Multica template" | 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/799 **Author:** [@enemyrr](https://github.com/enemyrr) **Created:** 4/17/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `multica-clean` --- ### 📝 Commits (1) - [`30d789c`](https://github.com/Dokploy/templates/commit/30d789cb452848191b2a8ac073494cfeb40eba58) Add Multica template ### 📊 Changes **4 files changed** (+136 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/multica/docker-compose.yml` (+68 -0) ➕ `blueprints/multica/multica.svg` (+7 -0) ➕ `blueprints/multica/template.toml` (+40 -0) 📝 `meta.json` (+21 -0) </details> ### 📄 Description ## Summary Adds a blueprint for [Multica](https://github.com/multica-ai/multica) — an open-source managed agents platform for teams (assign tasks to AI coding agents like Claude Code, Codex, OpenClaw, etc.). ## Services - **postgres** — `pgvector/pgvector:pg17` - **backend** — Go API + WebSocket server, port 8080 (built from `https://github.com/multica-ai/multica.git#main` with `Dockerfile`) - **frontend** — Next.js 16, port 3000 (built with `Dockerfile.web`) Multica doesn't publish pre-built images yet, so the template builds from the remote git context — same pattern `firecrawl/nuq-postgres` uses. ## Traefik domains Two public domains are exposed: - `${app_domain}` → `frontend:3000` - `${api_domain}` → `backend:8080` (needed by the `multica` CLI/daemon) `NEXT_PUBLIC_WS_URL` is baked into the frontend build pointing at `wss://${api_domain}/ws`. ## Login Out of the box, non-production environments accept verification code `888888` for any email. For production, set `RESEND_API_KEY` / `RESEND_FROM_EMAIL`. ## Test plan - [ ] PR preview deploys successfully - [ ] Import template into a Dokploy instance, deploy - [ ] Open `app_domain`, log in with `888888` - [ ] Verify backend is reachable at `api_domain`  <h3>Greptile Summary</h3> Adds a new Multica blueprint — a three-service stack (postgres/pgvector, Go backend, Next.js frontend) that builds from the upstream git repo since no pre-built images are published. The template structure (dual-domain variables, `[config.env]` table, healthcheck on postgres) is consistent with existing multi-domain templates like typebot. The only deviations from AGENTS.md conventions are: `ports` used instead of `expose` for both application services, and the missing `version: "3.8"` field at the top of `docker-compose.yml`. Both are minor style concerns with no impact on runtime behavior. <h3>Confidence Score: 5/5</h3> Safe to merge; all findings are P2 style/convention issues with no runtime impact. All three comments are P2 — `ports` vs `expose` and the missing `version` field are documented conventions in AGENTS.md but have no functional effect on Dokploy deployments. No logic bugs, security issues, or data-integrity problems were found. blueprints/multica/docker-compose.yml — minor style fixes for ports and version field <sub>Reviews (1): Last reviewed commit: ["Add Multica template"](https://github.com/dokploy/templates/commit/30d789cb452848191b2a8ac073494cfeb40eba58) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28760128)</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-23 03:38:11 -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#2911