[omnimus]

Sorry but we were not talking about “rsyncing the files over”. We are talking about what services that i've used like Forge or Ploi do where you deploy project into separate folder and then switch symlink. You can even roll it back.

I have a feeling you want to dunk on poor dumb PHP developer but like Forge is by the people who created Laravel. I believe they would put some thought into it. Maybe just maybe small chance of one bad request is not such a bad deal.

[kstrauser]

It is literally exactly the same issue, just with slightly less of an error window. I don't think those devs are poor and dumb, but I do think it's likely they've been working in environments where production errors are more tolerated than in other environments.

> Maybe just maybe small chance of one bad request is not such a bad deal.

If your company is OK with that, seriously, sincerely, right on! Keep doing this and move on to other problems.

[omnimus]

I had thought about it and you are just pulling my nose.

If you have very long database query and you update your app in middle of it using blue-green load balancer you get to same production error. It is the same thing just implemented slightly differently because of PHP characteristics allow this and with different systems you have to use different strategy.

So yeah have good feeling about us PHP devs having bad deployment strategies.

[kstrauser]

That is… exactly wrong. I encourage you to consider why that would not be the case.

[spdionis]

It is not the same issue, due to how opcache works. No one remotely competent runs PHP without opcache in 2025.