π³ Docker 360 β Week 14 of 16 | Same stack for every developer
π― Learning Objective
βMeray laptop par to chal raha tha!β β ye jumla har team ne suna hai. Is week me tum seekhoge ke Docker Compose override files se dev aur prod configs ko kaise alag rakha jaye, volumes se live code reload kaise mile, seed scripts se har developer ko same database data kaise mile, aur poori team ke liye ek repeatable workflow kaise banaya jaye. End tak tumhare paas ek aisa template hoga jo naye team member ko pehle din se productive bana de.
π¨ Visual Diagrams
Override files ka merge concept:
docker-compose.yml docker-compose.override.yml
(BASE β sab ke liye) (DEV ONLY β auto-merge hoti hai)
βββββββββββββββββββββββ ββββββββββββββββββββββββββββββββ
β services: β β services: β
β web: β β web: β
β build: . β + β volumes: β
β ports: β β - .:/app (live β
β - 8000:8000 β β command: uvicorn β
β db: β β --reload code!) β
β image: pg:16 β β environment: β
βββββββββββββββββββββββ β - DEBUG=1 β
ββββββββββββββββββββββββββββββββ
β docker compose up (dono auto-merge!)
βΌ
ββββββββββββββββββββββββββββββββββββββββββββββββββββ
β FINAL CONFIG β
β web: build + ports + volumes + reload + DEBUG β
β db: postgres 16 β
ββββββββββββββββββββββββββββββββββββββββββββββββββββ
PROD me override ko SKIP karo:
docker compose -f docker-compose.yml -f docker-compose.prod.yml up -d
Team workflow β sab ke paas same stack:
Developer A (Linux) ββ
β
Developer B (Mac) ββββΌβββΊ git clone β cp .env.example .env β docker compose up
β β
Developer C (Win) ββββ βΌ
βββββββββββββββββ
β web (reload) β
β db (seeded) β βββ same everywhere β
β cache (redis) β
βββββββββββββββββ
π§ Theory Deep Dive
Override files kaise kaam karti hain?
Jab tum docker compose up chalate ho, Compose khud ba khud in files ko merge kar deti hai (agar mojood hon):
docker-compose.yml(yacompose.yaml) β base configdocker-compose.override.ymlβ dev-specific changes
Merge deep hota hai: mappings (jaise environment) merge hote hain, jabke sequences (jaise ports) replace ho jati hain. Iska matlab ye hai ke base file me production jaisi clean config rakho, aur dev wali cheezen (bind mounts, debug flags, reload commands) override me.
Prod deploy ke waqt override ko explicitly skip karo:
docker compose -f docker-compose.yml -f docker-compose.prod.yml up -d
Volume sync strategies
| Strategy | Kya hai | Kab use karo |
|---|---|---|
Bind mount (.:/app) | Host ka code container me live | Dev me code reload ke liye |
Named volume for deps (/app/node_modules) | Container ki installed deps ko bind mount se bachana | Node/Python projects me |
.dockerignore | Build context se junk bahar | Hamesha β tez builds ke liye |
Named volume for DB (pgdata:/var/lib/postgresql/data) | Data container delete hone par bhi rahe | Dev databases ke liye |
Classic Node trick β bind mount host ke node_modules ko overwrite na kare:
services:
web:
volumes:
- .:/app
- /app/node_modules # anonymous volume: container wali deps mehfooz
Iska matlab ye hai ke host par node_modules mojood ho ya na ho, container apni installed dependencies use karega.
Database seed scripts
Postgres image /docker-entrypoint-initdb.d/ me rakhi .sql aur .sh files ko pehli dafa (jab data volume khaali ho) automatically chala deti hai:
services:
db:
image: postgres:16
environment:
POSTGRES_USER: dev
POSTGRES_PASSWORD: devpass
POSTGRES_DB: devdb
volumes:
- pgdata:/var/lib/postgresql/data
- ./db/init:/docker-entrypoint-initdb.d:ro
Numbering (01-schema.sql, 02-seed.sql) se order control hota hai. Har developer ko same schema + same sample data β parity ka yehi matlab hai.
Healthcheck + seed container pattern
Agar seed logic complex ho (API calls, etc.), ek one-shot container banao jo DB ke healthy hone ka wait kare:
services:
db:
healthcheck:
test: ["CMD-SHELL", "pg_isready -U dev -d devdb"]
interval: 5s
retries: 10
seed:
build: .
depends_on:
db:
condition: service_healthy
command: python /app/seed.py
π» Hands-On Lab
Ek complete dev stack banate hain: FastAPI app (live reload) + seeded Postgres.
Lab 1 β Project setup
Step 1: Project structure banao:
mkdir -p /tmp/team-stack/app /tmp/team-stack/db/init && cd /tmp/team-stack
Step 2: app/main.py likho:
from fastapi import FastAPI
import socket
app = FastAPI()
@app.get("/")
def home():
return {"message": "Hello from the team stack!", "served_by": socket.gethostname()}
@app.get("/health")
def health():
return {"status": "ok"}
Step 3: app/requirements.txt:
fastapi
uvicorn[standard]
psycopg2-binary
Step 4: Dockerfile:
FROM python:3.12-slim
WORKDIR /app
COPY app/requirements.txt .
RUN pip install --no-cache-dir -r requirements.txt
COPY app/ .
EXPOSE 8000
CMD ["uvicorn", "main:app", "--host", "0.0.0.0", "--port", "8000"]
Step 5: db/init/01-schema.sql:
CREATE TABLE IF NOT EXISTS users (
id SERIAL PRIMARY KEY,
name TEXT NOT NULL,
role TEXT NOT NULL
);
Step 6: db/init/02-seed.sql:
INSERT INTO users (name, role) VALUES
('Ali', 'developer'),
('Sara', 'designer'),
('Ahmed', 'devops')
ON CONFLICT DO NOTHING;
Lab 2 β Base + override compose files
Step 7: docker-compose.yml (base β prod jaisi clean config):
services:
web:
build: .
ports:
- "8000:8000"
depends_on:
db:
condition: service_healthy
db:
image: postgres:16
environment:
POSTGRES_USER: dev
POSTGRES_PASSWORD: devpass
POSTGRES_DB: devdb
volumes:
- pgdata:/var/lib/postgresql/data
- ./db/init:/docker-entrypoint-initdb.d:ro
healthcheck:
test: ["CMD-SHELL", "pg_isready -U dev -d devdb"]
interval: 5s
retries: 10
volumes:
pgdata:
Step 8: docker-compose.override.yml (sirf dev ke liye):
services:
web:
volumes:
- ./app:/app # live code reload
environment:
- DEBUG=1
command: uvicorn main:app --host 0.0.0.0 --port 8000 --reload
Step 9: .env.example (team me commit hoti hai) aur .dockerignore:
# .env.example β copy karke .env banao, .env ko git me mat dalo
cat > .env.example <<'EOF'
POSTGRES_USER=dev
POSTGRES_PASSWORD=devpass
POSTGRES_DB=devdb
EOF
cp .env.example .env
cat > .dockerignore <<'EOF'
.git
__pycache__
*.pyc
.env
EOF
Step 10: Stack up karo:
docker compose up --build -d
sleep 8
curl -s localhost:8000/
β
Expected result: {"message":"Hello from the team stack!",...} β app chal rahi hai.
Lab 3 β Live reload ka magic
Step 11: Code edit karo bina rebuild ke:
sed -i 's/Hello from the team stack!/Hello TEAM - edited live!/' app/main.py
sleep 3
curl -s localhost:8000/
β
Expected result: Naya message foran nazar aayega β --reload ne file change detect karke server restart kar diya. Iska matlab ye hai ke dev loop seconds ka hai, minutes ka nahi.
Lab 4 β Seeded data verify karo
Step 12:
docker compose exec db psql -U dev -d devdb -c "SELECT * FROM users;"
β Expected result: Ali, Sara, Ahmed wali 3 rows β har developer ke paas yehi data hoga, chahe wo duniya ke kisi kone me ho.
Lab 5 β Override merge ko inspect karo
Step 13:
docker compose config --services
docker compose config | grep -A5 'command:'
β
Expected result: Merge hui final config me command: uvicorn ... --reload aur volume mount dono nazar aayenge β proof ke override apply hui.
Step 14: Prod-style run (override skip):
docker compose -f docker-compose.yml up -d --force-recreate
docker compose exec web ps aux | grep -c "[u]vicorn"
docker compose down -v
β
Expected result: Prod mode me --reload nahi chalega β sirf base config active hogi. (Demo ke baad down -v se safai.)
β Checkpoint
Q1: docker compose up chalane par kaunsi files auto-merge hoti hain?
A: docker-compose.yml (base) aur docker-compose.override.yml (agar mojood ho) β override dev-specific changes ke liye hoti hai.
Q2: Bind mount ke sath Node project me /app/node_modules anonymous volume kyun lagate hain?
A: Taake host ka (ya missing) node_modules folder container ki installed dependencies ko overwrite na kar de.
Q3: Postgres seed scripts kab chalti hain β har restart par ya sirf pehli dafa? A: Sirf pehli dafa, jab data volume khaali ho. Isi liye seed change karne ke baad volume delete karna parhta hai.
Q4: Naye team member ke liye ideal onboarding steps kya honge is setup me?
A: git clone, cp .env.example .env, docker compose up β bas. Koi βpehle ye install karo, phir wo version set karoβ wali kahani nahi.
π Next Week
Week 15 me hum GPUs ko containers me layenge aur MLflow se experiments track karenge β ML workloads ka Docker wala hissa! βοΈ