blog-nest/infra/README.md

Infrastructure Directory

This directory contains all production and development infrastructure configurations for the blog-nest monorepo.

Files

Dockerfile

Multi-stage Docker build configuration for backend (NestJS) and frontend (Next.js).

• Base Image: node:24-alpine
• Stages: backend-build → backend-prod, frontend-build → frontend-prod

Build from root:

docker build -f infra/Dockerfile -t blog-nest:latest .

docker-compose.yml

Base configuration with shared service definitions. Contains common settings for both development and production environments.

docker-compose.override.yml

Development overrides - automatically loaded by Docker Compose CLI when running docker-compose up. Includes:

• Development container names (with _dev suffix)
• Hot-reload code volumes
• Published ports for local access
• Debug logging level

docker-compose.prod.yml

Production overrides - applied only when explicitly specified. Includes:

• Production container names
• Health checks with longer intervals
• Restricted port access (localhost only)
• Logging volumes
• SSL/TLS configuration
• Default fallback values for credentials

Usage

Development

cd infra
docker compose up

Or from root:

docker compose -f infra/docker-compose.yml -f infra/docker-compose.override.yml up

Production

docker compose -f infra/docker-compose.yml -f infra/docker-compose.prod.yml up -d

Structure

The three-file approach eliminates duplication:

• docker-compose.yml = base + shared config
• docker-compose.override.yml = dev-specific overrides (auto-loaded)
• docker-compose.prod.yml = prod-specific overrides (explicit)

nginx.conf

Nginx reverse proxy configuration with:

• SSL/TLS support (Let's Encrypt ready)
• Rate limiting (API: 100r/s, Web: 50r/s)
• Gzip compression
• Security headers
• Caching strategies
• Health check endpoint

Quick Start (VPS)

1. Copy files to VPS

scp -r infra/ user@vps:/home/deploy/blog-nest/

2. Create environment file

# On VPS, in /home/deploy/blog-nest/infra/
cp .env.example .env
# Edit .env with your values

3. Setup SSL certificates

# From infra directory
mkdir -p ssl

# If using Let's Encrypt (run once)
sudo certbot certonly --standalone \
  -d yourdomain.com \
  -d www.yourdomain.com

# Copy certs
sudo cp /etc/letsencrypt/live/yourdomain.com/fullchain.pem ./ssl/cert.pem
sudo cp /etc/letsencrypt/live/yourdomain.com/privkey.pem ./ssl/key.pem
sudo chown deploy:deploy ./ssl/*
sudo chmod 600 ./ssl/key.pem

4. Start services

cd /home/deploy/blog-nest/infra
docker compose -f docker-compose.prod.yml up -d

5. Verify health

docker compose -f docker-compose.prod.yml ps
curl http://localhost/health

Environment Variables

Create .env file in this directory:

# Database
DB_USER=blog_user
DB_PASSWORD=your_secure_password_here
DB_NAME=blog_production

# Redis
REDIS_PASSWORD=your_redis_secure_password_here

# Frontend
NEXT_PUBLIC_API_URL=https://yourdomain.com/api

# Logging
LOG_LEVEL=info

Production Checklist

• Ubuntu 24.04 LTS VPS deployed
• Docker & Docker Compose installed
• SSL certificates obtained (Let's Encrypt)
• .env file created with strong passwords
• Nginx config updated with your domain
• Database backups configured
• Firewall rules set (UFW)
• SSH hardened
• Services running and healthy
• DNS pointing to VPS IP
• Monitoring setup (optional)

Common Commands

# View logs
docker compose -f docker-compose.prod.yml logs -f

# Restart services
docker compose -f docker-compose.prod.yml restart

# Stop all
docker compose -f docker-compose.prod.yml down

# Database backup
docker compose -f docker-compose.prod.yml exec postgres \
  pg_dump -U blog_user blog_production | gzip > backup.sql.gz

# SSH into container
docker compose -f docker-compose.prod.yml exec api sh

See Also

• ../DEPLOY_VPS.md — Complete VPS deployment guide