hackforla / hackforla/peopledepot
Create deployment docker setup (for dev env)
- Dominant language
- Python
- Stars
- 14
- Forks
- 37
- Avg merge
- 9d 15h
- Merged PRs (30d)
- 5
Description
### Overview
We need to add a separate deployment docker setup so that we can use it for automated deployment eventually. Differences are ~~disabling debug variable~~, don't install development packages, etc.
### Action Items
- [ ] Create deployment Dockerfile and associated, docker-compose.yml and entrypoint.sh
- [ ] setup whitenoise for static files hosting
- [ ] Dockerfile with multi-stage build if it reduces docker image size
- [ ] requirements file with no development dependencies
- [ ] ~~Check off this issue's item in #218~~
### Resources/Instructions
- ~~This issue is part of #218~~
- [production dockerfile in django dockerizing guide](https://testdriven.io/blog/dockerizing-django-with-postgres-gunicorn-and-nginx/#production-dockerfile) (Most of these are from the testdriven.io site)
- [Django static files guide](https://testdriven.io/blog/django-static-files/)
- [Django Docker for deployment guide with a whitenoise section](https://testdriven.io/blog/deploying-django-to-heroku-with-docker/#whitenoise)
- [How to test whitenoise config](https://whitenoise.readthedocs.io/en/stable/django.html#how-do-i-know-it-s-working)
- [Deploying whitenoise where django is not at the root of the domain](https://whitenoise.readthedocs.io/en/stable/django.html#deploying-an-application-which-is-not-at-the-root-of-the-domain) might be useful or we might need it if merging the changes breaks the deployed environment for this reason.
- [Example whitenoise changes that's part of the Testdriven.io "Django REST Framework and Docker" course](https://github.com/fyliu/django-tdd-docker/commit/2e36357812627d09b510abc008258891ba22b4ad)
- Also see the [whole course as git commit history](https://github.com/fyliu/django-tdd-docker/commits/main/).
Contributor guide
Assessment
This issue has not been assessed yet.