I have deployed this setup with the desire to expose the nuxt build through the caddy reverse-proxy. AND not expose the API.
Both nuxt and the api are on a bridge network.
compose.yaml
networks:
prod:
name: prod
driver: bridge
services:
nuxt:
container_name: nuxt
ports:
- "3000:3000"
build:
dockerfile: Dockerfile.prod
context: ../nuxt
depends_on:
- api
networks:
- prod
environment:
- FASTAPI_BASE_URL=api:8000
api:
container_name: fastapi
build:
context: ../fastapi
networks:
- prod
ports:
- "8000:8000"
api’s Dockerfile
FROM python:3.10
WORKDIR /app
COPY requirements.txt .
RUN pip install -r requirements.txt
COPY . /app
EXPOSE 8000
CMD ["uvicorn", "main:app", "--host", "0.0.0.0", "--port", "8000"]
nuxt’s Dockerfile.prod
### STAGE 1: Build ###
FROM node:latest AS build
COPY . /app
WORKDIR /app
RUN npm install
RUN npm run generate
### STAGE 2: ENV ###
FROM build AS base
WORKDIR /app
COPY --from=build /app/.output/public /app
COPY .env /app/.env
EXPOSE 3000
CMD ["npx", "serve", "./"]
Caddyfile
{
email info@example.com
}
app.example.com {
reverse_proxy localhost:3000
}
The Nuxt build works, but the api calls that it makes is made to app.example.com.
I’m sure there are best practices of this somewhere, but I haven’t been able to find any.
Thank you for reading and here’s to hoping you know what’s missing!
