mirror of
https://github.com/Dokploy/templates.git
synced 2026-07-16 11:25:25 +02:00
0ada7ae5f2
The Multica backend is an API-only chi server with no route registered at "/", so the generated backend domain (path "/") permanently answered HTTP 404 even though the container was healthy. The web frontend already proxies /api/*, /ws, /auth/* and /uploads/* to http://backend:8080 via Next.js rewrites, and when NEXT_PUBLIC_WS_URL is unset the browser derives the WebSocket URL from the page origin, so the backend never needs to be exposed publicly. - drop the backend [[config.domains]] entry and api_domain variable - drop NEXT_PUBLIC_WS_URL so the WS URL falls back to the page origin and goes through the frontend's /ws rewrite - remove ephemeral host port publications (ports: "8080"/"3000"); Traefik reaches the containers over the docker network Verified on a Dokploy instance: deploy done, frontend / -> 200 and backend reachable through the proxy (/api/config -> 200). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
33 lines
806 B
TOML
33 lines
806 B
TOML
[variables]
|
|
app_domain = "${domain}"
|
|
jwt_secret = "${password:64}"
|
|
postgres_password = "${password:32}"
|
|
|
|
[config]
|
|
[[config.domains]]
|
|
serviceName = "frontend"
|
|
port = 3000
|
|
host = "${app_domain}"
|
|
path = "/"
|
|
|
|
[config.env]
|
|
POSTGRES_DB = "multica"
|
|
POSTGRES_USER = "multica"
|
|
POSTGRES_PASSWORD = "${postgres_password}"
|
|
JWT_SECRET = "${jwt_secret}"
|
|
FRONTEND_ORIGIN = "https://${app_domain}"
|
|
ALLOWED_ORIGINS = "https://${app_domain}"
|
|
MULTICA_APP_URL = "https://${app_domain}"
|
|
RESEND_API_KEY = ""
|
|
RESEND_FROM_EMAIL = "noreply@multica.ai"
|
|
GOOGLE_CLIENT_ID = ""
|
|
GOOGLE_CLIENT_SECRET = ""
|
|
GOOGLE_REDIRECT_URI = "https://${app_domain}/auth/callback"
|
|
NEXT_PUBLIC_GOOGLE_CLIENT_ID = ""
|
|
COOKIE_DOMAIN = ""
|
|
S3_BUCKET = ""
|
|
S3_REGION = "us-west-2"
|
|
CLOUDFRONT_DOMAIN = ""
|
|
CLOUDFRONT_KEY_PAIR_ID = ""
|
|
CLOUDFRONT_PRIVATE_KEY = ""
|