5,838
edits
Category:Cumulus MX: Difference between revisions
→Installing Cumulus MX: Added "what I did"
(→Installing Cumulus MX: Added "what I did") |
|||
| Line 37: | Line 37: | ||
= Installing Cumulus MX = | = Installing Cumulus MX = | ||
There is no automatic installer (this may change). Cumulus MX is supplied as a zipped package | There is no automatic installer (this may change). Cumulus MX is supplied as a zipped package on a link from [[software|download page]]. | ||
== Requirements for running on Windows == | == Requirements for running on Windows == | ||
| Line 65: | Line 56: | ||
**On Linux you will need library libudev.so.0 which may not be installed by default. Installing package libudev0 may resolve this. There may be issues if you are using a 64-bit version of Linux. I'm not sure what the resolution is at the moment, if this is the case. | **On Linux you will need library libudev.so.0 which may not be installed by default. Installing package libudev0 may resolve this. There may be issues if you are using a 64-bit version of Linux. I'm not sure what the resolution is at the moment, if this is the case. | ||
== Completely new MX installation == | |||
Create a new directory (recommended name CumulusMX) and unzip the contents of the download package into it. | |||
== Changing from Cumulus 1 to MX == | |||
# Two alternatives | |||
#*Just create a new directory (recommended name CumulusMX) and unzip the contents into it. Then copy over your existing data files and your Cumulus.ini file, and any other configuration files that you may have created (e.g. strings.ini, twitter.txt etc). | |||
#* Alternatively, to run Cumulus MX with your existing Cumulus data, take a back up copy of your existing Cumulus directory, and then unzip Cumulus MX into the original Cumulus folder. | |||
#If your "Cumulus.ini" was actually called "cumulus.ini" you should rename it to start with a capital letter. | |||
#See pages already referenced for how to edit your '''.ini''' files to work with MX. | |||
== What I did == | |||
I have used Cumulus 1 for a decade or so, and been very happy with it, but I wanted to give MX a go without affecting my Cumulus 1 installation. Here is exactly what I did, step by step. | |||
#I downloaded the '''CumulusMXDist3069''' zip from [[Software#Current_Release|the Current Release section]] on the downloads page. | |||
#I unzipped the contents (on my Windows PC) into a partition I use just for software downloads | |||
#I used a package that verifies the files it copies to duplicate the folder '''CumuluxMX''' onto the drive where I run Cumulus. I then noticed that the package contained some very obsolete copies of some external packages: | |||
#*In "\CumulusMX\interface\lib\jquery" it contained jQuery version 1.9.1, that is 2014 vintage and very obsolete, so I downloaded latest compressed production version from [https://jquery.com/download/ jQuery web site]. I prefixed the version in the MX package with the word OBSOLETE (OBSOLETEjquery-latest.min.js) and renamed the version I had downloaded (jquery-3.4.1.min.js) to the old name in the correct path (on my Windows PC) "\CumulusMX\interface\lib\jquery\jquery-latest.min.js". | |||
#*Similarly, the MX package contained obsolete vintage version 2.1.4 (2015-03-10) of Highstocks and Highcharts, so I downloaded latest versions from [https://www.highcharts.com/blog/download/ the Highstock link] on this page. I then created a new folder obsolete at "\CumulusMX\interface\lib\highstock\js", moved the folders "modules" and "themes" that were there in my new folder, and the various highstock and highchart files that were there were moved into the obsolete folder. Now I navigated to the code folder within that download, copied the files within it to "\CumulusMX\interface\lib\highstock\js" and then copied the folders "modules" and "themes" from that code download folder into the same location. So now (in March 2020) everything is related to version 8.04 released 10 March 2020. | |||
#The locale I used for Cumulus 1 is going to be the same I will use for MX (same PC!) so my copying across of my existing files is easy: | |||
#* I copy '''\Cumulus\Cumulus1.ini''' to ''\CumulusMX'' folder as "Cumulus.ini". I then edit the MX "Cumulus.ini" file: | |||
#**First , where in the "[FTP site]" (yes, mine was named correctly with second word all lowercase) I change any references to web pages within "Cumulus" folder to say within "CumulusMX" folder. | |||
#**Second, where I want a transfer done only at end of day, I need to change that | |||
#*The file "\CumulusMX\Reports\.gitignore" is joined in the Reports folder by what I currently have in "\Cumulus\Reports". These are another "Cumulus.ini" and the existing monthly and annual NOAA reports. I don't need to change those file names as I will continue to use the same format (see change to main Cumulus.ini mentioned above). | |||
= Updating to a new MX release = | = Updating to a new MX release = | ||