Docker Compose & Nginx Config Generator

Runs in your browserNo sign-up required

App service name

Container port

Host port (what you visit locally)

Database

DB name

DB user

DB password

DB host port

Include Redis

Extra environment variables (one per line, KEY=value)

docker-compose.yml

services:
  app:
    build: .
    ports:
      - "3000:3000"
    depends_on:
      - db
    environment:
      - NODE_ENV=production
      - DATABASE_URL=postgresql://myapp_user:changeme@db:5432/myapp
    volumes:
      - .:/app
      - /app/node_modules

  db:
    image: postgres:16-alpine
    restart: unless-stopped
    environment:
      - POSTGRES_DB=myapp
      - POSTGRES_USER=myapp_user
      - POSTGRES_PASSWORD=changeme
    ports:
      - "5432:5432"
    volumes:
      - db-data:/var/lib/postgresql/data

volumes:
  db-data:

Two Config Files Most Developers Write From Memory (Badly)

A basic app-plus-database docker-compose.yml and an Nginx reverse-proxy config are two of the most commonly needed, least often perfectly-remembered config files in web development — most developers end up searching for an old project or a Stack Overflow answer to copy from. This tool builds both from a short guided form instead, correctly wired (service dependencies, environment variables, a working connection string, proper WebSocket-friendly proxy headers) every time.

Frequently Asked Questions

Will the generated docker-compose.yml work as-is?

It assumes your app has a Dockerfile in the same directory (`build: .`) — you'll still need that, since it's specific to your app's language and setup. The compose file itself handles the service wiring: ports, environment variables, the database service, and a DATABASE_URL pointed at it.

Do I need to change the default database password?

Yes, always — the generated password is a placeholder. Replace it before deploying anywhere beyond your own local machine, ideally by moving it into an environment variable or secrets file rather than committing it directly into docker-compose.yml.

Does the Nginx config actually set up SSL certificates?

No — it generates the config block pointing at where Let's Encrypt certificates are typically stored, but you still need to run Certbot (or your certificate provider's equivalent) separately to actually obtain and install the certificates at those paths.

What does client_max_body_size control?

The maximum size of a request body Nginx will accept before rejecting it — this matters if your app accepts file uploads. The default Nginx limit (1MB) is too small for most upload features, which is why it's exposed as a setting here.

Docker Compose & Nginx Config Generator

Two Config Files Most Developers Write From Memory (Badly)

Frequently Asked Questions

Related Tools