5,838
edits
m (further re-sequence) |
|||
Line 33: | Line 33: | ||
You can download and unzip in advance, but cannot replace existing files while they are being used, so how you stop MX is in next two sub-sections. | You can download and unzip in advance, but cannot replace existing files while they are being used, so how you stop MX is in next two sub-sections. | ||
My preference, after download, and unzip into a holding area, is to copy (it would be file transfer if you download on another device) over my existing installation all files except: | |||
*CumulusMX.exe | |||
*CumulusMX.exe.config | |||
while MX is still running. I then stop MX for minimal time needed to replace just those two files before I restart MX. That way I minimise downtime, especially useful for a patch release when few files have changed, as it takes some time to replace all the files in the installation. | |||
For simplicity, in guidance below, MX is stopped before any files are replaced. | |||
==Upgrading if you run MX as a service== | ==Upgrading if you run MX as a service== | ||
Don't forget to stop the service, before you | Don't forget to stop the service, before you do the upgrade. | ||
For a Linux Operating system: <code>sudo systemctl stop cumulusmx</code>. | For a Linux Operating system: <code>sudo systemctl stop cumulusmx</code>. | ||
For Microsoft Windows Operating System: | |||
==Upgrading if you run MX interactively== | ==Upgrading if you run MX interactively== | ||
If you do NOT run as a service, you will want to use '''Control and C''' to make the software close tidily. | If you do NOT run as a service, you will want to use '''Control and C''' in the terminal (or command) window running MX to make the software close tidily. | ||
edits