5,838
edits
Updating MX to new version: Difference between revisions
m
further re-sequence
m (→Introduction to updating MX: re-sequence) |
m (further re-sequence) |
||
| Line 8: | Line 8: | ||
Cumulus MX has been updated so frequently in 2020, that you may be used to updating to a new build, and for you this article is not useful. | Cumulus MX has been updated so frequently in 2020, that you may be used to updating to a new build, and for you this article is not useful. | ||
=Where to download a release distribution= | |||
==Latest release== | |||
Download release distribution zip from [[Software|the Software article in this Wiki]] for latest version. | |||
Be aware that the developer needs to remember to update this link each time there is a new release. | |||
An image that contains a '''Rapberry Pi lite operating system''' and the latest Cumulus MX release already included, may be downloaded from the same wiki article. | |||
==Any release developed by Mark Crossley== | |||
Download release distribution zip from https://github.com/cumulusmx/CumulusMX/releases for earlier versions. | |||
=Introduction to upgrading MX= | =Introduction to upgrading MX= | ||
| Line 124: | Line 140: | ||
The important point to make here is that when you do an update, you should copy in '''ALL''' files from the release distribution you want to run next. This is because there are dependencies between files within a distribution, so missing out any particular file may stop other files from working. However, if you are skipping versions, read the in-between release announcements to see if there are any one-off actions. | The important point to make here is that when you do an update, you should copy in '''ALL''' files from the release distribution you want to run next. This is because there are dependencies between files within a distribution, so missing out any particular file may stop other files from working. However, if you are skipping versions, read the in-between release announcements to see if there are any one-off actions. | ||
= What to read (and when) before upgrading = | |||
= What to read (and when) before | |||
== Updating from immediately preceding build == | == Updating from immediately preceding build == | ||
| Line 359: | Line 303: | ||
Treat like any other major version upgrade as described above. | Treat like any other major version upgrade as described above. | ||
= Knowing when a new release is available = | |||
== CREDIT == | |||
Thanks to ''Billy'' on support forum for suggesting text for this section. | |||
== Using forum notifications == | |||
As new releases are announced in [https://cumulus.hosiene.co.uk/viewtopic.php?f=40&t=17887 Cumulus MX Announcements and Download - PLEASE READ FIRST] topic, you can use the spanner tool to '''subscribe''' to this topic to receive notifications of a new post announcing a new release (or any other release-related announcement). | |||
== MX terminal message == | |||
If ... | |||
#...you have a monitor to see the terminal output from the Cumulus MX engine (Windows calls this either a command window, powershell window, or a terminal window depending on how you invoke it, for Unix-based implementations this is the output window when using the terminal functionality), AND | |||
#...your device running MX is connected to internet, AND | |||
#...your MONO (if not Windows) is not obsolete (SSL certificate out of date), AND | |||
#...you restart MX | |||
... then you will see a prompt when a new version of MX is available. | |||
It is worth stressing that if you leave MX running, then this feature will leave you blissfully unaware that an update is available; it only checks when MX is restarted. | |||
== MXDiags == | |||
In addition ... | |||
#...if you can view the MXdiags file for the current session of MX, AND | |||
#... MX is running with connection to the internet, AND | |||
#...you restart MX | |||
... if a new version of MX is available, the MXDiags file will say so (the message is not easy to spot as there is a lot of output before it, and variation in what output appears before it). Anyway, here is one example, just one example as in my experience '''the message has appeared at different places for each of the recent updates'''): | |||
<pre> | |||
2020-05-27 04:18:48.326 Calculating sunrise and sunset times | |||
2020-05-27 04:18:48.326 Sunrise: 04:58:11 | |||
2020-05-27 04:18:48.326 Sunset : 21:19:54 | |||
2020-05-27 04:18:48.326 Tomorrow sunrise: 04:57:08 | |||
2020-05-27 04:18:48.326 Tomorrow sunset : 21:21:11 | |||
2020-05-27 04:18:48.388 You are not running the latest version of CumulusMX, build 3080 is available. | |||
2020-05-27 04:18:48.763 Station type:</pre> | |||
There is no message in whatever place it can appear ... | |||
*... if you are using latest version, OR | |||
* ... if you are not connected to the internet, OR | |||
*... if you keep MX running all the time! | |||
== Start/Stop script == | |||
When the '''Status''' option of this script is used, whenever a new release of MX is available, it will output a message. | |||
== Dashboard in MX Admin Interface == | |||
In recent releases, one of the alarm indicators shown at the bottom of the dashboard page of the administrative interface, will flash red when you are not running latest build, and glow green when there is no newer release compared to the one you are running. | |||
== Web Tags == | |||
Since 3.7.0 release of MX, two relevant web tags have become available: | |||
* <#NewBuildAvailable> Returns a boolean value | |||
** 0 - MX running the latest build available | |||
** 1 - MX is running an earlier build than the latest public release | |||
* <#NewBuildNumber> Displays the latest public release build number | |||
= Recommended Actions when Updating = | = Recommended Actions when Updating = | ||