I know this sounds absurd but bare with me: It would be great to have the same version of PHP allowed in multiple php?_release positions. Maybe it could be a no-op (path already exists so skip it?).
Here's my use case: I have php4_release currently unassigned, and php1_release set to 5.6. I need to start moving clients off the default 5.6 for new domains. I want to change php1_release to 7.3 or 7.4.
Ideally I just script something that walks through every domain config, setting the PHP version of domains that don't have a default set, to PHP=4, which I've gone ahead and set to 5.6 (the same as PHP=1).
Then once that's done, rewrite confs, everyone who was on PHP1 with 5.6 is now on PHP4 with 5.6 and I'm free to upgrade php1_release to the latest. No downtime.
Without this (correct me if I'm wrong), switch the versions in options.conf, ./build php d, then rewrite configs. During this time, clients with an explicit version of PHP1 or no explicit version (ending up on PHP1 by default) may end up on a super-new version of PHP until I have time to correct it.
Thoughts?
Here's my use case: I have php4_release currently unassigned, and php1_release set to 5.6. I need to start moving clients off the default 5.6 for new domains. I want to change php1_release to 7.3 or 7.4.
Ideally I just script something that walks through every domain config, setting the PHP version of domains that don't have a default set, to PHP=4, which I've gone ahead and set to 5.6 (the same as PHP=1).
Then once that's done, rewrite confs, everyone who was on PHP1 with 5.6 is now on PHP4 with 5.6 and I'm free to upgrade php1_release to the latest. No downtime.
Without this (correct me if I'm wrong), switch the versions in options.conf, ./build php d, then rewrite configs. During this time, clients with an explicit version of PHP1 or no explicit version (ending up on PHP1 by default) may end up on a super-new version of PHP until I have time to correct it.
Thoughts?