Docker-ness

[tkell]

I've got a version, at simple-tornado-server that has a Dockerfile that works locally. You can also run it locally by running a three-line bash script.

Along the lines of @alnesbit's comments on not wanting to lock ourselves in to AWS or GCP, it seems like maybe the thing to do is to create Readmes / Docker infrastructure to help people run everything from a DIY bash-script version to a massively scaled Docker swarm/stack/wombat/cluster/etc version.

I would like to summon @psobot for his feelings about this, and also for his feelings about running both the webserver and the queue process in the same Docker container vs. running two containers.

(Two containers feels more "correct" to me, but it is also much more work? )

[psobot]

running both the webserver and the queue process in the same Docker container vs. running two containers.

The main advantages of running in two containers would be:

• Being able to test the webserver container in isolation
• Being able to test the queue process in isolation
• Would allow users to spawn a queue container on a different machine (or multiple queue workers) without extra web servers and their dependencies

I went down this road with The Wub Machine and ended up having two containers (well, 10 or so, but one for the generic "queue worker" concern) and it's been much easier to iterate on the separate parts of the app. The webserver container will probably also be much lighter than the queue worker, faster to upload, faster to run through CI, and so on.

---

^{One of these days, I'll actually get around to reading/writing some code in this project, as I feel like I might have some Valuable Learnings™ to bring to the table, having solved this exact problem in this exact problem domain before.}

[tkell]

Got it, ty for your wisdom! I am going to keep building the ultra-simple single container one, and then we can go from there once it works.