3 ms·
Hi, Not really. That's why we love so much uwsgi. All you have to do is to add a new config file for your zerg server, and you are done. This is handled withou
by teleyinex 11y ago
Hi,
Not really. That's why we love so much uwsgi. All you have to do is to add a new config file for your zerg server, and you are done. This is handled without problems by supervisor and we've never experienced an issue with it.
I've another blog post about our full infrastructure, explaining specifically why we love uwsgi + supervisor. Because we don't need extra software within our stack and everything is pretty simple and runs on Python :D
- eli 11y agoBut I'm not running a zerg server right now (I don't think!) so it would be a new daemon even if it's part of an existing package, right? Looking forward to more blog posts. Uwsgi is new to me, but so far I've been very pleased with it. I've been considering solving deploys at a higher level by spinning up a new docker container and moving traffic from one to the other.
- teleyinex 11y agoYou only have to add a new daemon/process. Then you'll have this graceful reloading feature ;-) From my point of view is has less impact than booting a new container.