5 Commits

Author SHA1 Message Date
325394150d Point production at the LAN MongoDB (192.168.1.7:27017)
All checks were successful
Build and Deploy Nuxt / build (push) Successful in 8s
Production uses the network's database server instead of a mongo service
inside the stack (the compose-managed one never served the API). Dev is
unchanged: backend/.env keeps localhost:27017.

- docker-compose.yml: MONGO_URI=mongodb://192.168.1.7:27017/mathew; drop
  the in-stack mongo service, its volume and the healthcheck gate
- deploy.yml: up -d --remove-orphans so yesterday's mongo container is
  retired when the new compose lands
2026-10-02 00:07:03 +02:00
5a7537f449 Test?
Some checks failed
Build and Deploy Nuxt / build (push) Failing after 5s
2026-10-02 00:00:27 +02:00
4e80e15703 Add MongoDB to the stack and fix nginx upstream resolution
All checks were successful
Build and Deploy Nuxt / build (push) Successful in 11s
The backend image ships no .env (gitignored) and compose passed no env,
so MONGO_URI fell back to the container's own 127.0.0.1, the API died on
connect, and nginx answered 502 for every /api request.

- docker-compose.yml: mongo:7 service with a data volume; backend gets
  MONGO_URI=mongodb://mongo:27017/mathew and waits on its healthcheck
- nginx.conf: resolve service names through Docker's DNS per request
  (stale cached IPs 502 after every container recreate); match bare /api
  too so it cannot loop through the frontend's SSR proxy
2026-10-01 22:56:07 +02:00
1bd971232e jdksdksajdjs2
All checks were successful
Build and Deploy Nuxt / build (push) Successful in 34s
g
2026-10-01 22:43:32 +02:00
580a160300 Pipeline test
Some checks failed
Build and Deploy Nuxt / build (push) Failing after 30s
2026-10-01 21:34:56 +02:00