docker-compose พร้อม Postgres และ Redis

docker-compose defines many containers in one file, so Django, Postgres, and Redis start together with a single command. 🧩

Everything lives in docker-compose.yml, where each container you need becomes an entry under the services key.

Your web service builds from your Dockerfile and runs Django, the heart of the whole stack.

The db service uses the official Postgres image, giving you a real database without installing anything locally.

The redis service runs the official Redis image, ready to act as a cache or a Celery message broker.

Compose gives each service a DNS name, so Django reaches Postgres at the host db, not localhost.

Use depends_on so web starts after db and redis, keeping your startup order sane.

A named volume stores Postgres data outside the container, so your rows survive restarts and rebuilds.

Feed secrets and settings through environment or an env_file, keeping config out of your image.

The ports key forwards a container port to your machine, so you can open the app in a browser.

Run docker compose up and the entire stack boots together; add -d to run it in the background.

How does your web container reach the database in Compose?

You wired a full stack in docker-compose: web, db, and redis services, connected by name, with volumes for data and one command to launch. 🚀