Coolify's Traefik defaults to the 'coolify' network, but the frontend was only on the per-resource network -> Traefik couldn't reach it (000/empty reply). Join the external coolify network + set traefik.docker.network=coolify.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Frontend was on two networks; Traefik (on only one) couldn't reach it -> 000/empty reply on HTTPS while nginx served 200 directly. Letting Coolify manage networking puts both services on its single proxy network; service-name DNS (backend) still resolves.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Coolify runs compose with --project-directory=repo-root, so context:.. resolved above the repo and the build context/Dockerfiles weren't found. Root compose + context:. matches the Dockerfiles' assumption (context = repo root).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Container-ready via docker/ compose (frontend nginx + backend Node). Compose adjusted for Coolify on the prod server: frontend uses expose:80 (no host binding — host 8080 is taken by the Coolify proxy; Traefik routes visigine.de), backend ALLOWED_ORIGINS=https://visigine.de. Secrets stay in server/.env (git-ignored); see server/.env.example.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
