osem-fcy/docker-compose.yml

version: '3.5'

services:

  database:
    container_name: osem-db
    image: postgres:11
    volumes:
      - pg-data:/var/lib/postgresql/data

  web:
    container_name: osem-web
    build:
      context: .
      args:
        CONTAINER_USERID: 1000
    command: /osem/bin/osem-init.sh
    depends_on:
      - database
    ports:
      - 3000:3000
    volumes:
      - .:/osem

volumes:
  pg-data:
Implementing multistage build Dockerfile 2019-03-18 23:27:01 -03:00			`version: '3.5'`
Introduces openSUSE based docker-compose environment 2018-09-05 22:49:57 +02:00
			`services:`
Implementing multistage build Dockerfile 2019-03-18 23:27:01 -03:00
Introduces openSUSE based docker-compose environment 2018-09-05 22:49:57 +02:00			`database:`
Implementing multistage build Dockerfile 2019-03-18 23:27:01 -03:00			`container_name: osem-db`
			`image: postgres:11`
			`volumes:`
			`- pg-data:/var/lib/postgresql/data`

			`web:`
			`container_name: osem-web`
Docker cleanups - Put docker-compose.yml into version control, no need to make this an example file and complicate things. - Start the docker dev-env osem on port 3000. Just as our documentation says and how we do it in vagrant. - hardcode CONTAINER_USERID so you don't have to have an docker-compose.override.yml if your UID is 1000. - Rename web service/container to osem for clarity in the logs - Keep assets also in a volume in production - warn a bit more prominently about docker-compose.override.yml 2018-09-12 22:38:07 +02:00			`build:`
			`context: .`
			`args:`
			`CONTAINER_USERID: 1000`
Fix service name in compose override Services names should match between the config and the override file... 2019-01-29 21:22:19 +01:00			`command: /osem/bin/osem-init.sh`
Introduces openSUSE based docker-compose environment 2018-09-05 22:49:57 +02:00			`depends_on:`
			`- database`
			`ports:`
Docker cleanups - Put docker-compose.yml into version control, no need to make this an example file and complicate things. - Start the docker dev-env osem on port 3000. Just as our documentation says and how we do it in vagrant. - hardcode CONTAINER_USERID so you don't have to have an docker-compose.override.yml if your UID is 1000. - Rename web service/container to osem for clarity in the logs - Keep assets also in a volume in production - warn a bit more prominently about docker-compose.override.yml 2018-09-12 22:38:07 +02:00			`- 3000:3000`
Introduces openSUSE based docker-compose environment 2018-09-05 22:49:57 +02:00			`volumes:`
			`- .:/osem`
Implementing multistage build Dockerfile 2019-03-18 23:27:01 -03:00
			`volumes:`
			`pg-data:`