Multi-Stage Dockerfile and Local Compose Stack

Write a local development stack and a production-shaped Docker build for this app. They are different files with different jobs. APP Language and framework: [NEXT.JS | ASTRO | FASTAPI | OTHER] Package manager: [PNPM | NPM | BUN | PIP] Services the app needs locally: [POSTGRES, REDIS, MAILPIT — edit] Port the app listens on: [PORT] Env vars required at boot: [LIST] Persistent data: [DB VOLUME | UPLOADS] Health: [PATH THAT RETURNS 200 WHEN READY] DELIVER 1) Dockerfile, multi-stage. deps → build → runtime. Pin the base image by major. Run as a non-root user in the final stage. Copy only the output needed to run. Include a note on where lockfile installs go so builds cache. 2) .dockerignore that actually changes the context size (git, node_modules, tests, local env files). 3) compose.yaml for local dev: app with a bind mount and a dev command (not the production server), database with a named volume and a healthcheck, and depends_on with the healthy condition. Mail catcher if I listed one. 4) A second compose profile or override note for running the production image locally, so we do not confuse "works in dev mount" with "the image boots." 5) Environment example file with comments, no real secrets, and a line that says which vars are public. 6) Commands: first boot, reset the database volume, and follow logs. 7) Three footguns for this framework in Docker (file watching on the mount, NEXT_PUBLIC_ baked at build, native addons) and which of them this setup addresses. Do not put secrets in the image. Do not use latest as the only tag.