Add Multica template

[enemyrr]

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.

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

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)

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	30d789c

[greptile-apps]

ports instead of expose

AGENTS.md lists this under "Docker Compose Conventions (CRITICAL): NEVER include: ports (use expose only)". Both backend (line 27) and frontend (line 62) use ports. Since Dokploy's Traefik proxy handles external routing via the [[config.domains]] config, expose is sufficient for inter-container reachability and keeps the port off the host network.

Suggested change

	ports:
	- "8080"
	expose:
	- "8080"

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

ports instead of expose (frontend)

Same issue as the backend service — should use expose per AGENTS.md conventions.

Suggested change

	- "3000"
	environment:
	expose:
	- "3000"

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Missing version: "3.8"

AGENTS.md states the Compose version field MUST be 3.8. Roughly 200+ existing blueprints include it. While Docker Compose v2 treats this field as obsolete, it's still the documented convention for this repo.

Suggested change

	name: multica
	version: "3.8"
	name: multica