view docker/docker-compose.yml @ 3535:337e9f85f84c

Prevent non-erased gauge version to have empty validity range This is a follow-up to revision ba0339118d9c, that did not introduce such constraint by virtue of missing that we have the information which gauge is 'current' readily at hand in the erased flag.
author Tom Gottfried <tom@intevation.de>
date Wed, 29 May 2019 18:41:35 +0200
parents 7ebd4154894e
children
line wrap: on
line source

# If you fiddle around with the following error message:
# Version in "./docker-compose.yml" is unsupported
#
# Option 1)
# Update docker and docker compose to at least docker version 17.12.0+.
#
# Option 2)
# Change version: "3.5" to version: "3"
# And delete the name configuration form `networks:` below.
#
version: "3.5"
services:
  gemma_db:
    container_name: gemma-db
    build:
      context: ../
      dockerfile: docker/Dockerfile.db
    image: "gemma_db"
    volumes:
    - ../schema:/opt/gemma
    networks:
    - gemma
    ports:
    - "54321:5432"
  gemma_geoserver:
    container_name: gemma-geoserver
    build:
      context: ../
      dockerfile: docker/Dockerfile.geoserv
    depends_on:
      - gemma_db
    image: "gemma_geoserver"
    networks:
    - gemma
    ports:
     - "8280:8080"
  gemma_backend:
    container_name: gemma-backend
    build:
      context: ../
      dockerfile: docker/Dockerfile.backend
    depends_on:
      - gemma_db
      - gemma_geoserver
    image: "gemma_backend"
    volumes:
    - ../:/opt/gemma
    networks:
    - gemma
    ports:
     - "8200:8000"
  gemma_spa:
    container_name: gemma-spa
    build:
      context: ../
      dockerfile: docker/Dockerfile.spa
    depends_on:
      - gemma_backend
      - gemma_geoserver
    image: "gemma_spa"
    volumes:
    - ../client:/opt/gemma/client
    networks:
    - gemma
    ports:
     - "8290:8080"

networks:
  gemma:
      # name: gemma needs at least docker version 17.12.0+
      # API version: "3.5"
      # https://docs.docker.com/compose/compose-file/#name-1
      name: gemma