Docker deployment

​

Architecture

​

docker-compose.yml

​

Dockerfile

• PostgreSQL and MySQL PDO extensions
• Composer for dependency management
• Supervisord for process management (PHP-FPM + queue workers)
• Proper file permissions for storage/ and bootstrap/cache/

​

Deployment steps

​

1. Configure environment

cp .env.example .env

APP_ENV=production
APP_DEBUG=false
APP_URL=https://api.exowpee.com

DB_HOST=db
DB_PORT=5432
DB_DATABASE=exowpee
DB_USERNAME=exowpee
DB_PASSWORD=secure_password_here

QUEUE_CONNECTION=database
CACHE_STORE=database

​

2. Build and start

docker compose up -d --build

​

3. Run initial setup

docker compose exec app php artisan migrate --seed
docker compose exec app php artisan jwt:secret
docker compose exec app php artisan config:cache
docker compose exec app php artisan route:cache

​

4. Verify

curl http://localhost:8000/v1/auth/user/login \
  -H "Content-Type: application/json" \
  -d '{"username": "admin@exowpee.com", "password": "password"}'

​

Nginx configuration

• FastCGI proxy to PHP-FPM on the app container
• Static asset serving from public/
• CORS headers for bundled assets
• Proper try_files for Laravel routing

​

Data persistence

volumes:
  postgres_data:
    driver: local

​

Database backups

# Dump database
make db-dump

# Or manually
docker compose exec db pg_dump -U exowpee exowpee > backup.sql

# Restore
docker compose exec -T db psql -U exowpee exowpee < backup.sql

​

Makefile commands

​

Production considerations

1. Use a managed database instead of Docker PostgreSQL for production
2. Add SSL termination (via a load balancer or Nginx with Let’s Encrypt)
3. Configure log rotation for application and Nginx logs
4. Set up monitoring for container health and resource usage
5. Use Redis instead of database for cache and queue in production
6. Run queue workers as separate containers for scalability