dockerizing-django
dockerizing-django copied to clipboard
realpython
This PR references .env file removal request #36 and by itself references #24, as now everything is set in docker-compose.yml file, what is not nice is that variables are duplicated...
Would there be a way to update the project code without "rebuilding" the image while in dev? The "mount volume to project directory" would not quite work with docker-machine, correct?
The .env file at the root of the repo has special use: https://docs.docker.com/compose/env-file/ The file is sourced when docker-compose is invoked, and the values affect docker-compose commands. My suggestion is...
Hi, I just noticed that, with the current setup, debug mode is enabled in production. More specifically: https://github.com/realpython/dockerizing-django/blob/master/web/docker_django/settings.py#L26 should probably be something like `DEBUG = True if os.getenv('DEBUG') == 'True'...
https://github.com/realpython/dockerizing-django/blob/master/docker-compose.yml wrote ``` redis: restart: always build: ./redis ports: - "6379:6379" ``` I think this may expose 6379 to the whole internet? Although in production.yml changed to ``` ports: -...
Would it be possible to include an example of documentation on how to run unit tests when building the containers? I can submit a pull request for this, but wasn't...
When I create and run the container, I run the tests to check the result. But when I make a change, it is not reflected and shows the same result....
In your guide you have: ``` $ docker-compose build $ docker-compose -f production.yml up -d $ docker-compose run web /usr/local/bin/python manage.py migrate ``` But shouldn't that be? ``` $ docker-compose...
`run` does not works on Windows and `exec` works well on Windows too.
