The Docker image made by this Dockerfile is suitable for trying out the project,
but not suitable for dev/production as it directly clones the git repo.
Even so, it still should
[ ] 1. automatically run createsuperuser
To make a Dockerfile suitable for dev,
[ ] 1. one should be able to reflect changes to the docker image more easily.
[ ] 2. to do that, we shouldn't git clone but instead copy source from local
[ ] 3. and use volumes to reflect local changes in code real time
[ ] 4. use volumes to maintain changes to DB while running container
[ ] 5. Use Docker Compose instead of Makefile
To make a Dockerfile suitable for prod, there should be:
[ ] 1. some secret-management (Hashicorp Vault or AWS KMS)
[ ] 2. NGINX support (probably need to use docker-compose)
[ ] 3. Separate Dockerfiles for dev and prod and ci
The Docker image made by this Dockerfile is suitable for trying out the project, but not suitable for dev/production as it directly clones the git repo.
Even so, it still should
To make a Dockerfile suitable for dev,
To make a Dockerfile suitable for prod, there should be: