cr-connect-workflow/postgres/docker-compose.yml

version: "3.7"
services:
  db:
    image: postgres
    volumes:
      - ./pg-init-scripts/initdb.sh:/docker-entrypoint-initdb.d/initdb.sh
      - $HOME/docker/volumes/postgres:/var/lib/postgresql/data
    ports:
      - 5432:5432
    environment:
      - POSTGRES_USER=${DB_USER}
      - POSTGRES_PASSWORD=${DB_PASS}
      - POSTGRES_MULTIPLE_DATABASES=crc_dev,crc_test,pb,pb_test
Gets docker-compose working. You'll need to add a .env file to the same directory as the docker-compose.yml file that sets the values for DB_USER and DB_PASS. 2020-02-05 02:42:09 +00:00			`version: "3.7"`
			`services:`
			`db:`
			`image: postgres`
			`volumes:`
			`- ./pg-init-scripts/initdb.sh:/docker-entrypoint-initdb.d/initdb.sh`
			`- $HOME/docker/volumes/postgres:/var/lib/postgresql/data`
			`ports:`
			`- 5432:5432`
			`environment:`
			`- POSTGRES_USER=${DB_USER}`
			`- POSTGRES_PASSWORD=${DB_PASS}`
It became impossible to use the Swagger ui when we started adding authentication to all of the calls. I discovered Connexion and Swagger have a default way of handing JTW authentication and this cleans up our code quite a bit, moves the securing of endpoints into the API Definition, which is quite nice, and removes a whole library dependency (I never get to do that!) I added a SWAGGER_AUTH_KEY that can be used in non-production environments to allow users to quickly authenticate from the Swagger ui. I also removed all api calls to simple little happy api services, because that is just mean and pointless. 2020-03-24 18:15:21 +00:00			`- POSTGRES_MULTIPLE_DATABASES=crc_dev,crc_test,pb,pb_test`