Problem: cannot be deployed using docker

This is being addressed by PR https://github.com/dativebase/old-pyramid/pull/5.

The underlying issue is that the OLD does not conform to the 12-factor App approach. This will be accomplished when the following is complete (maybe more):

[x] Configuration can be accomplished fully via environment variables.
[x] Logging is improved and logs are sent to stdout for later routing and aggregation.
[x] The OLD is stateless, meaning that a single pserve (waitress/Pyramid/OLD) process can handle requests for multiple logically distinct OLD instances, i.e., database and disk path pairs.
[x] A Dockerfile exists which can install the OLD and all of its Python and OS dependencies.
[x] Beaker is configured to use MySQL (maybe Redis ultimately) so that multiple OLD processes can be serve requests for multiple logical OLDs and the sessions for these OLDs can remain distinct.
[x] Functional tests have been written to confirm the correct stateless behaviour of the OLD: data goes to the correct database, correct place on disk, and sessions are not muddled. See https://github.com/dativebase/old-pyramid/blob/cbbc39cf8e5057c9b1bf6f52af2aa12461d169e7/old/tests/functional/test_multiple_olds.py.

Related requirements for an entrypoint repo ("dativebase"?):

[x] A Docker Compose config file exists which can be used to reproducibly create OLD development deployments. See https://github.com/dativebase/dativebase/blob/master/docker-compose/docker-compose.yml.
[x] A Makefile exists which makes it easy to install dependencies, initialize specific databases, construct filesystem scaffolding for a specific OLD instance, restart the OLD, etc. See https://github.com/dativebase/dativebase/blob/master/docker-compose/Makefile.

dativebase / old-pyramid

Problem: cannot be deployed using docker #4