Currently the docker container contains a supervisor process, which runs all the processes we need.
This can cause issues (losing all the data in redis when it restarts), and is also not very docker-like.
We should rather set this up as described in the docker-django-bootstrap readme: https://github.com/praekeltfoundation/docker-django-bootstrap . That way we can have separate containers for each component and link them together, as well as take advantage of all the tools that the base image provides us with.
It might also be better to create a casepro-docker repo to house all of this in, and just to pull whatever casepro code we want, to keep the casepro codebase and the specific docker configuration separate.
Currently the docker container contains a supervisor process, which runs all the processes we need.
This can cause issues (losing all the data in redis when it restarts), and is also not very docker-like.
We should rather set this up as described in the docker-django-bootstrap readme: https://github.com/praekeltfoundation/docker-django-bootstrap . That way we can have separate containers for each component and link them together, as well as take advantage of all the tools that the base image provides us with.
It might also be better to create a casepro-docker repo to house all of this in, and just to pull whatever casepro code we want, to keep the casepro codebase and the specific docker configuration separate.