Pyoto

The goal is to run Pyoto without playing with reverse-proxy configurations and be able to setup better resource scaling. With a modern web server you can run WSGI apps and control the number of workers needed to scale to your need, or even have all workers stop when the app is useless. We have in mind using Fusion Passenger which allows fine control over the workers.

The Pyoto daemon would be run separately, and the web server would then handle running the frontend workers by itself.

Thus, we would need to split the startup code, and ensure to decouple common resources (like logs).