Timeline for Where does wordpress gets its core and plugin updates
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 28, 2017 at 16:26 | comment | added | Mark Kaplun | that doesn't make much sense. If the upgrade is manual, what is exactly the big issue with just downloading it via FTP/SVN/GIT. The extra 10 minutes that it will require are not even a blip on the time being usually wasted in such orgs. Side effect of the firewall is that you will not get notifications about updates as well, but this also is solvable for anything worthy to be installed. And yes, your backup to staging plan is exactly what you should do, welcome to the big league. | |
| Apr 28, 2017 at 15:49 | comment | added | Eric | the installation is on a VM, separate from the rest of their network, And no the updates will NOT be automated, but the servers need to be reached in order to manually core update when needed (after being tested on a staging machine which does have access to the updates. And of course i could : - backup the production machine - send that backup to the staging machine and restore it there - do the update on the staging machine - backup the staging machine end send back the archive to be restored on prod. (4 Gb of data each way, yay). I'd just rather not. | |
| Apr 28, 2017 at 15:21 | history | answered | Mark Kaplun | CC BY-SA 3.0 |