osem-fcy/docker-compose.yml

version: "2"

services:
  database:
    image: postgres
    environment:
      PGDATA: /var/lib/postgresql/data/pgdata
  osem:
    build:
      context: .
      args:
        CONTAINER_USERID: 1000
    command: /osem/bin/osem-init.sh 
    depends_on:
      - database
    ports:
      - 3000:3000
    volumes:
      - .:/osem
Introduces openSUSE based docker-compose environment 2018-09-05 22:49:57 +02:00			`version: "2"`

			`services:`
			`database:`
			`image: postgres`
			`environment:`
			`PGDATA: /var/lib/postgresql/data/pgdata`
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			`osem:`
			`build:`
			`context: .`
			`args:`
			`CONTAINER_USERID: 1000`
Introduces openSUSE based docker-compose environment 2018-09-05 22:49:57 +02:00			`command: /osem/bin/osem-init.sh`
			`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`