Refactor and clean compose files
- use same postgres container for dev and test (create 2 different databases) - use docker-compose.override.yml to avoid duplication - ignore more files not needed in the docker image By default docker-compose reads both docker-compose.yml and docker-compose.override.yml. In docker-compose.override.yml we mount the current directory as a volume for development. To test the image we only use docker-compose.yml: - don't force port 5432 to the outside world to avoid conflict - do not mount the current directory
Showing
- .dockerignore 6 additions, 2 deletions.dockerignore
- .env 1 addition, 1 deletion.env
- Jenkinsfile 2 additions, 2 deletionsJenkinsfile
- Makefile 12 additions, 7 deletionsMakefile
- README.rst 20 additions, 8 deletionsREADME.rst
- docker-compose-test.yml 0 additions, 21 deletionsdocker-compose-test.yml
- docker-compose.override.yml 19 additions, 0 deletionsdocker-compose.override.yml
- docker-compose.yml 4 additions, 13 deletionsdocker-compose.yml
- postgres/create-test-db.sh 7 additions, 0 deletionspostgres/create-test-db.sh
- tests/functional/conftest.py 1 addition, 1 deletiontests/functional/conftest.py
Loading
Please register or sign in to comment