Category:Cumulus MX: Difference between revisions

Category:Cumulus MX (view source)

Revision as of 10:53, 18 May 2020

569 bytes added , 10:53, 18 May 2020

m

→‎Updating to a new MX release

Sfws

5,838

edits

@@ Line 588: / Line 588: @@
 = Updating to a new MX release =
-If you have a monitor to see the output from the Cumulus MX engine in its console log, you will see a prompt when a new version is available. Equally if you can view the MXdiags file for the current session of MX, that will say if a new version of MX is available.
+If you have a monitor to see the output from the Cumulus MX engine (Windows call this a console window, Unix-based implementations call this the output terminal window), you will see a prompt when a new version is available. Equally if you can view the MXdiags file for the current session of MX, that will say if a new version of MX is available. Obviously if you are using latest version, you do not see this message!
-*If your update is from the immediately previous build, then just check the release announcement in the support forum, or the entry at [[Cumulus_MX_formal_release_versions]] in this wiki (if that is up to date) for which files have been affected.
+*If your update is from the immediately previous build, then just check the release announcement in the support forum, or the précis style entry at [[Cumulus_MX_formal_release_versions]] in this wiki (if that is up to date) for which files have been affected. The actual release announcement will be more informative telling you if the upgrade requires one-off actions (like changing the schema if you use a database, or editing your web pages to take advantage of new web tags). The release announcement may sometimes include scripts to download and run to perform one-off actions.
-*If your update is skipping some intermediate versions, then check the corresponding release announcements or Wiki entries for every version since the one you have been using before planning your upgrade.
+*If your update is skipping some intermediate versions, then check the corresponding release announcements or Wiki entries for every version since the one you have been using before planning your upgrade. Again there may be one-off actions required at particular in-between versions.
 It is always best to take a backup of your existing MX installation before you do an update, this allows you to regress back to the earlier version if you mess up installing the new version.