Dockerizing for quick deployment

[almereyda]

Last year I've unsuccessfully tried to Dockerize the OSM Tasking Manager 2 for quick deployment in changing environments.

The main problem was the dependency on some PostGIS dependencies, esp. in terms of splitting data and the web service into several containers.

I am filing this issue for documentary reasons.

This issue may relate to hotosm/hotosm-project-ideas#15

[chebizarro]

A better approach might be to break up the different components into separate containers and use Docker Compose to manage them. I am looking into it over the weekend, do you have any more specific details on what problems you had in your attempt?

[kriscarle]

I have a working Docker setup in my fork at https://github.com/mapforenvironment/osm-tasking-manager2

I have 3 containers: postgres, web app, and a nginx reverse proxy gateway. Most of the settings are passed in via environment variables that are used to create the local.ini and production.ini dynamically as the container starts. The exception being the oauth consumer key/secret, which would need to be pulled out as a config.

Happy to submit a PR, but I think there are a few decisions to be made first regarding whether you want a single container or multiple, if it needs to be production ready (e.g. on port 80 instead of 6543) etc.

[almereyda]

@kriscarle Thanks for responding back. And @chebizarro sorry for not having been aware of your answer.

I believe a loosely-coupled approach, i.e. with docker-compose as mentioned, suits most deployment scenarios most. This said I would suggest to create an extra repository for all Docker related files and folders and add an orchestration example with -compose.

Production and Development scenarios could then be represented with different *.yaml files.

[dbdean]

There is a pull request to make this work with docker at #980, it would be nice to see it merged, or at least get some feedback.