5 ms·
>> Because deploying a PHP app is mostly just dropping files into a directory and restarting a web server. Lots of solutions can't "just restart a web server"
by skeeter2020 5y ago
>> Because deploying a PHP app is mostly just dropping files into a directory and restarting a web server.
Lots of solutions can't "just restart a web server" as part of their deployment.
- tyingq 5y agoYes, I didn't claim it as an absolute. Lots of solutions can restart a web server or a PHP-fpm instance without trouble. Or use things other than containers to manage zero downtime.
- Groxx 5y agoLots of solutions don't want to - that's fairly different than "can't". I dare say few companies need nigh-100% uptime, and it costs an incredible amount both in setup and in maintenance to go from "10s outage while updating" to "no downtime while updating".
- conradfr 5y agoAlternatively you can change the symlink to your www directory to the new one.
- miltondts 5y agoWhat exactly do you mean? How do these solutions deal with servers unexpectedly going down? I worked on telecom where you need the service to be up 24/7 and we restarted all the services on deployment. In waves of course.
- maxk42 5y agoWhat do you think the net effect of deploying a new container image is? At some point the server goes down and a new copy is loaded. You could always disable opcaching and then you wouldn't even have to restart the server to deploy a new PHP instance.
- danudey 5y agoDepends on how you set it up, but with a lot of container orchestration these days, you create a new image then point your load balancer at that instead, giving you a clean blue/green deploy without downtime.
- 908B64B197 5y agoYou can always spin a new one and have the load balancer redirect requests.
- icedchai 5y agoWith most PHP setups, you can usually skip the restart part.