With something like this, how do you handle the period of time while copying? I mean you can’t really leave it running as it wouldn’t be in a consistent state. A “under maintenance” page instead? Copy to a fresh folder and when done tell the webserver to serve the new location?
YOLO: especially with thugs like PHP you only affect one page at a time and with low traffic the odds of a problem is small
Maintenance page: temporarily show a page. Some servers like IIS have this built in. Otherwise it’s a simple update to httpd conf
In a cluster environment, just take the node you’re updating out of rotation, and only update one node at a time.
Copy and switch like you suggested. Can be combined with any of the above and is a smart move if upload is slow or can be interrupted, or it’s cumbersome to restore the old files
Thanks, yeah I’m well aware that this is not a problem in proper setups. I was just wondering what a company that is large enough to care about downtime and at the same time has staff manually click around in filezilla would do.
With something like this, how do you handle the period of time while copying? I mean you can’t really leave it running as it wouldn’t be in a consistent state. A “under maintenance” page instead? Copy to a fresh folder and when done tell the webserver to serve the new location?
It depends. I’ve done it a few different ways:
Edit: spelling
Typically either downtime or taking the server off of the load balancer, depending on scale.
All of this is automated in modern container orchestration tools like kubernetes, though.
Thanks, yeah I’m well aware that this is not a problem in proper setups. I was just wondering what a company that is large enough to care about downtime and at the same time has staff manually click around in filezilla would do.