2 ms·

I think the "right" answer here is to put something like nginx in front with load balancing, and rolling restarts, or something like that. I'm in a very simila

by dimino 10y ago

I think the "right" answer here is to put something like nginx in front with load balancing, and rolling restarts, or something like that. I'm in a very similar situation as what you've got described, and I'll start in on that part of the project sometime in the next month or so. Also been looking at Elastic Beanstalk for deployments. Have you looked at that yet?

StavrosK 10y ago
Yes, I think the way to do that is to have nginx switch new requests to the updated app server, and shut down the first one when it's not serving requests any more. I don't know how you'd communicate with nginx inside the container to tell it to switch, though, or how you would be able to know when all requests were done on the old container. Hopefully there's an easy way. Too bad that a single SIGHUP becomes so complicated with containers, but I guess it's a tradeoff. About the Beanstalk, I haven't looked into it too much, maybe that can help with deployment. I'd be grateful if you could let me know how it worked, if you ever try it out.