5,838
edits
Category:Cumulus MX: Difference between revisions
m
→Updating to a new MX release
m (→MySQL settings) |
|||
| Line 481: | Line 481: | ||
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 you mess up installing the new version. | ||
Best way is to rename your current install directory, then unzip the new release, letting it create a new '''CumulusMX''' folder. Copy across Cumulus.ini into that new directory, and then copy the contents of the '''data''' and '''Reports''' directories from your ''current install'' to the new install. | Best way is to rename your current install directory, then unzip the new release, letting it create a new '''CumulusMX''' folder. Copy across Cumulus.ini into that new directory, and then copy the contents of the '''data''' and '''Reports''' directories from your ''current install'' to the new install. However, if you are downloading on a different device, or on a different disc to where you are running MX, then after downloading simply copy the changed files into the existing MX directory on the device where you run MX. | ||
If you have edited any files, see if the release notice says that file has been revised, if it has not then keep your edited file by not copying in the replacement file within the zip. If the release revises a 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. This includes any web pages you might have edited to give the look you desire, or the content you want (e.g. adding rain this month to this month page, or combining this month and this year page). If you have done major customisation to the standard website then you probably have your equivalents to the standard web page in a different directory and use '''Extra Files''' to specify where they are, so the new MX will still find them. If you have done any customisation to the '''interface''' then copy across just the files that you have customised of the ''interface folder from the current installation'' to the new installation - but be careful with this one, as many releases change the interface in some way and you must not lose any vital functionality. | If you have edited any files, see if the release notice says that file has been revised, if it has not then keep your edited file by not copying in the replacement file within the zip. If the release revises a 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. This includes any web pages you might have edited to give the look you desire, or the content you want (e.g. adding rain this month to this month page, or combining this month and this year page). If you have done major customisation to the standard website then you probably have your equivalents to the standard web page in a different directory and use '''Extra Files''' to specify where they are, so the new MX will still find them. If you have done any customisation to the '''interface''' then copy across just the files that you have customised of the ''interface folder from the current installation'' to the new installation - but be careful with this one, as many releases change the interface in some way and you must not lose any vital functionality. | ||
| Line 488: | Line 488: | ||
Finally, don't delete your old installation for a week or so as you may notice something from the older version that you haven't copied across! | Finally, don't delete your old installation for a week or so as you may notice something from the older version that you haven't copied across! | ||
== Updating if you use the start/stop management script == | |||
1. look on [[Software|Software download page]], find the link to latest version, and fill out the '...' below appropriately as you run these 2 commands on your device where you do downloads: | |||
<pre>cd /tmp | |||
wget https://github.com/cumulusmx/CumulusMX/ ... .zip</pre> | |||
2. Once that download is complete, start cumulusmx.sh with option -u | |||
<pre>/home/pi/CumulusMX/cumulusmx.sh -u</pre> | |||
3.When asked for the zip file, enter | |||
<pre>/tmp/CumulusMXDist</pre> and hit the TAB Button | |||
4.Choose the zip file with the CumulusMX update and hit return. | |||
5. Follow the on screen instructions | |||
6. With each update component .....you can choose: [y]es, [n]o, [A]ll, [N]one, [r]ename | |||
I would recommend select '''A''' as that will simply replace all files without further action. | |||
CumulusMX will be restarted after update completes. | |||
You can check if the update was successful by using option -s: | |||
<pre> /home/pi/CumulusMX/cumulusmx.sh -s</pre> | |||
= User Interface = | = User Interface = | ||