mirror of
https://github.com/Dokploy/templates.git
synced 2026-05-22 22:44:09 -05:00
[PR #798] [CLOSED] Add Multica template #2106
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/798
Author: @enemyrr
Created: 4/17/2026
Status: ❌ Closed
Base:
main← Head:add-multica-template📝 Commits (5)
a36253bfeat(signoz): update Docker Compose and template for ClickHouse integration85803a2refactor(signoz): remove ClickHouse environment variables from Docker Compose and enhance template configuration2845cc4chore(signoz): update version to v0.98.0 in meta.json68d7814refactor(signoz): update Docker Compose and template for ClickHouse configuration3c2a5a2Add Multica template📊 Changes
6 files changed (+207 additions, -21 deletions)
View changed files
➕
blueprints/multica/docker-compose.yml(+68 -0)➕
blueprints/multica/multica.svg(+7 -0)➕
blueprints/multica/template.toml(+40 -0)📝
blueprints/signoz/docker-compose.yml(+23 -20)📝
blueprints/signoz/template.toml(+47 -0)📝
meta.json(+22 -1)📄 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
pgvector/pgvector:pg17https://github.com/multica-ai/multica.git#mainwithDockerfile)Dockerfile.web)Multica doesn't publish pre-built images yet, so the template builds from the remote git context — same pattern as
firecrawl/nuq-postgres.Traefik domains
Two public domains are exposed:
${app_domain}→frontend:3000${api_domain}→backend:8080(needed by themulticaCLI/daemon)NEXT_PUBLIC_WS_URLis baked into the frontend build at deploy time pointing atwss://${api_domain}/ws, so WebSocket traffic routes through the api domain.Login
Out of the box, non-production environments accept verification code
888888for any email. For production, setRESEND_API_KEY/RESEND_FROM_EMAIL.Test plan
app_domain, log in with888888api_domainmultica setup self-host --server-url https://<api_domain> --app-url https://<app_domain>Greptile Summary
Adds a new Multica blueprint (three services: pgvector/postgres, Go backend, Next.js frontend) with two auto-generated domains, strong auto-generated secrets, and all optional integrations (Resend, Google OAuth, S3/CloudFront) defaulting to empty strings. The template follows established two-domain and remote-build-context patterns already present in the repo (e.g.,
openpanel,firecrawl). The signoz files in the diff are pre-existing changes on the branch, not introduced in the latest commit.Confidence Score: 5/5
Safe to merge; only P2 style/documentation suggestions remain.
No P0 or P1 findings. The two remaining comments are P2: one about pinning the mutable
#mainbuild ref (acknowledged pattern in the repo), and one about documenting multi-line PEM key encoding for the optional CloudFront integration. Neither blocks functionality or deployment.blueprints/multica/template.toml — CLOUDFRONT_PRIVATE_KEY documentation; blueprints/multica/docker-compose.yml — build context pin.
Reviews (1): Last reviewed commit: "Add Multica template" | Re-trigger Greptile
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.