5,838
edits
Category:Cumulus MX: Difference between revisions
m
→Updating to a new MX release
|
= Updating to a new MX release =
== MX output message ===
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), '''and your device running MX is connected to internet''', 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 is running with connection to the internet, that will say if a new version of MX is available. Obviously if you are using latest version, or not connected to the internet, you do not see this message!▼
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),
#..'''your device running MX is connected to internet''', AND
#...you restart MX
▲
There is no message in either place ...
*... if you are using latest version,
* ... if you are not connected to the internet, OR
* you do not restart MX!
== What to read before updating ==
*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. Again there may be one-off actions required at particular in-between versions.
== Back-ups ==
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.▼
▲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 either you mess up installing the new version, or the new version has a issue that prevents it working with the versions of other software (like MONO) that your installation uses.
== two approaches ==▼
▲== The two approaches ==
Some people upgrade by just copying in the files that the release announcement says have changed, others copy in all files from the downloaded zip. The first should only be used with caution, files like '''CumulusMX.exe.config''' can change between versions, but not be mentioned in a release announcement, and the developer will have been making edits to files since the previous release, and might forget exactly which files have been edited between releases. Also you may be upgrading from an earlier version and therefore be skipping several intermediate releases. You may be able to see the dates when files were changed within the zip and therefore be able to decide for yourself if you compare those dates with the previous release you were using if you have kept the download for the version you were using.
#*then David [https://cumulus.hosiene.co.uk/viewtopic.php?p=140355#p140355 (see this post)] recommends this different approach. After downloading a new release unzip it on the device/disc where you down load it. Next simply copy the files (optionally only those that have newer dates because they have changed) into the existing MX directory on the device where you run MX. Then you know all your existing files are there, and as mentioned you can choose to only copy in the minimum number of files as specified in the release notes (find them on [https://cumulus.hosiene.co.uk/viewtopic.php?f=40&t=17887 this forum] or in [[Cumulus_MX_formal_release_versions|Wiki here]]).
== Updating when files within release might overwrite your own edits ==
If you have edited any files, see if the release notice says that file has been revised, if it has not then it is easy to keep your edited file by not copying in the replacement file from within the zip. If the release revises any file you previously edited, take a backup of your edited file, before you copy the new file into your folder. You can then use a file comparing tool to see what has changed in the release and what you changed and hopefully manage to merge to a new file that keeps any functionality change in a new release and keeps your customisation.
== After update ==
Start the new installation of MX and watch out for any errors - If the device you run MX on has a monitor, then look in the terminal/command window. In all cases look at the latest file in the MXdiags folder to see if any errors are reported.
| |||