docker-compose.yml

version: "3.7"

volumes:
  postgres_data:
  redis_data:

networks:
  backend:

services:
  redis:
    image: redis:5.0-alpine
    ports:
      - ${REDIS_PORT:-6379}:6379
    volumes:
      - redis_data:/data
    networks:
      - backend
    command: redis-server
  postgres:
    image: postgres:10.6-alpine
    volumes:
      # We'll store the postgres data in the 'postgres_data' volume we defined:
      - postgres_data:/var/lib/postgresql/data
    networks:
      - backend
    ports:
      - ${PG_PORT:-5432}:5432
    environment:
      POSTGRES_PASSWORD: 3x4mpl3P455w0rd
  # Where are the rest of the app services? (i.e. test, worker, web, etc)
  #
  # We've separated the app services from the rest of the services to streamline
  # the CI/CD pipeline execution. You'll find the app service definitions on the
  # `docker-compose.override.yml` file.
  #
  # You don't have to do anything special to docker-compose or plis to make the
  # project work as usual. By default, `docker-compose` will read
  # `docker-compose.yml` and `docker-compose.override.yml` files, merging their
  # contents before doing any actual work.
  #
  # See https://docs.docker.com/compose/extends/#understanding-multiple-compose-files