[DevOps] Containerization: Multi-Stage Dockerfile & Local Development Stack

[AlAfiz]

Description: Write a production-ready, multi-stage Dockerfile to containerize the Node.js API, alongside a docker-compose.yml file that orchestrates the API, PostgreSQL, and Redis for seamless local development natively on Linux environments.
Context / Motivation: "It works on my machine" is an anti-pattern. We need a reproducible, containerized setup so new contributors can spin up the entire backend stack with a single docker compose up command.
Acceptance Criteria: - [ ] Create a Dockerfile that builds the TS code in an initial stage, then copies only the compiled JS and production dependencies into a lightweight runtime image (e.g., node:20-alpine).

• Create a docker-compose.yml linking the API service to postgres:15 and redis:7 containers.
• Map persistent volumes correctly so database data survives container restarts.
  Technical Pointers: Pay close attention to .dockerignore. Prevent node_modules and local .env files from being copied into the build context. Ensure the API container awaits the database startup before attempting connection.

[MoscowDev]

Hello,

I would like to implement a production-ready Docker setup for the Node.js API using a multi-stage Dockerfile and a docker-compose configuration to ensure a fully reproducible local development environment.

I have experience working with containerized Node.js applications, backend infrastructure, and Docker-based orchestration for multi-service systems, and I can deliver a clean and reliable setup aligned with best practices.

My approach will include:

• Creating a multi-stage Dockerfile:

  • A build stage that compiles TypeScript into JavaScript.
  • A production stage based on node:20-alpine that includes only compiled output and production dependencies.
  • Ensuring a minimal and secure runtime image.

• Writing a .dockerignore file to exclude node_modules, local .env files, and other unnecessary artifacts from the build context, improving build speed and security.

• Creating a docker-compose.yml file that orchestrates:

  • The Node.js API service
  • PostgreSQL 15 database container
  • Redis 7 cache container

• Configuring persistent volumes for PostgreSQL to ensure data survives container restarts.

• Ensuring proper service dependency management so the API waits for PostgreSQL and Redis to be ready before establishing connections (e.g., using health checks or wait strategies).

• Validating the setup so the entire stack can be started reliably with a single docker compose up command on Linux environments.

This implementation will provide a consistent, production-ready development environment that eliminates setup friction and ensures reproducibility across all contributors.

Best regards,
Nnaji Moses Ogomegbunam

[grantfox-oss]

🦊 GrantFox — @MoscowDev has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #173)
2. Your PR will be reviewed by the BETAIL-BOYS maintainers

Good luck! Track your progress on GrantFox.