This repository was archived by the owner on Jun 11, 2021. It is now read-only.
Fix non-existing postgres 'engine' database and wrong container name in docs #45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When trying to run this application
a) while running
docker-compose run engine python manage.py migrateI encountered this error message:
ERROR: No such service: enginesince the Django container is named
webindocker-compose.ymland notengine.This is fixed by renaming the relevant commands in the
appREADME.b) Startup errors (in the docker-compose logs) relating to the postgres database
enginenot existing.The reason for this is that the
postgrescontainer creates a DB namedpostgresby default. This pull request resolves that issue by addingPOSTGRES_DB: enginetodocker-compose.yml. Please note that I did not add those to all other compose configs likedocker-compose.prod.yml.Note: If you have already started up the container,
postgreswill not automatically re-initialize. You need to delete thepgdatavolume usingdocker volume rm app_pgdatabut note that deleting the volume WILL result in loss of all data already being in the database