Single compose base

[bufke]

The goal is to provide a minimal compose file base that is appropriate to extend for development, docker compose production, and kobo-install users. A bonus goal would be to allow for docker compose up to work in some use case without modification. An override file would be provided to production use cases.

TODO

• Break single compose file into fe/be base files that others extend. Create default docker-compose.yml that extends both bases.
• What to do with static files, they must be manually copied. Perhaps move this step to Dockerfile? Worse case, we document that the end user must run the command manually.

Design decisions

• Base file should not specify database versions. This may be convenient for developers as long as they aren't running very old versions. We do not wish to deploy old versions to new instances. We do not want to break kobo-install users constantly by incrementing.
• Base file will use one celery worker, convenient to developers and small instances.

For consideration

• Move PYTHONUNBUFFERED: 1 to kpi Dockerfile. Any reason that someone would want this disabled?
• Revamp documentation. This README is out of date and could be more helpful for a "I just want to run kobotoolbox" use case. It could instead of minimal quick set up steps for running kobo-docker in production and dev. With a link to more broad "How to install kobo" on our website.
• Create new migrations service (like helm chart)