5,838
edits
Migrating from Cumulus 1 to MX: Difference between revisions
Migrating from Cumulus 1 to MX (view source)
Revision as of 09:56, 31 July 2020
, 09:56, 31 July 2020→3: NEW LOCATION APPROACH
| Line 331: | Line 331: | ||
#*For a pi, the instruction might be <tt>unzip -o CumulusMXDist3'''nnn'''.zip</tt> where '''nnn''' is the last 3 digits of the build number. | #*For a pi, the instruction might be <tt>unzip -o CumulusMXDist3'''nnn'''.zip</tt> where '''nnn''' is the last 3 digits of the build number. | ||
#Then copy (or file transfer over) | #Then copy (or file transfer over) | ||
#* your | #* your previous '''data''' folder contents into the new data folder created by unzipping, | ||
#*your | #*your previous '''Reports''' folder contents (if any) into the new Reports folder created by unzipping | ||
#*your Cumulus.ini file, | |||
#** Check that destination file, it must be "Cumulus.ini" (ensure it starts with capital letter and all other letters are lower case) | |||
#** In the new "Cumulus.ini" edit any lines that made reference to the old windows location. Remember, that only windows uses "\" in paths, and your new device will require reference to new locations. Even if you are still using windows, you may need to make changes to reflect that the files are now in a new location. | |||
#**You can delay changing other settings (like the port used to access your weather station which uses a different parameter in MX) when you have access to the Settings pages in the MX admin interface | |||
#* any other configuration files that you may have created (e.g. strings.ini, twitter.txt etc). | |||
The big advantage of this approach is that anytime you are not running MX you can go back to Cumulus 1 and let it run from where it left off (subject to availability of past data in your weather station). Obviously you cannot run Cumulus 1 and MX at the same time accessing the same weather station. | |||
=== Editing files=== | === Editing files=== | ||