Category:Cumulus MX: Difference between revisions

151 bytes added ,  07:08, 20 March 2020
m
Line 87: Line 87:
#**# I change any references to web pages within "Cumulus" folder to say within "CumulusMX" folder.
#**# I change any references to web pages within "Cumulus" folder to say within "CumulusMX" folder.
#**# Next where I want a transfer done only at end of day, I have added lines like "ExtraEOD19=1" and changed the previous "ExtraRealtime19=1" to "ExtraRealtime19=0" (I previously used realtime as that was only way in Cumulus 1 to ensure a template file was processed so it held correct values as close to end of day as possible, but it inefficiently also made huge numbers of unwanted transfers during the day). I had 9 such files being copied far too often, so those 9 changes will cause a huge reduction in processing load!
#**# Next where I want a transfer done only at end of day, I have added lines like "ExtraEOD19=1" and changed the previous "ExtraRealtime19=1" to "ExtraRealtime19=0" (I previously used realtime as that was only way in Cumulus 1 to ensure a template file was processed so it held correct values as close to end of day as possible, but it inefficiently also made huge numbers of unwanted transfers during the day). I had 9 such files being copied far too often, so those 9 changes will cause a huge reduction in processing load!
#**# I have a few files that are PHP scripts listed in this section written as Cumulus templates; each has a number of PHP variables being set equal to a Cumulus web tag. In some cases the web tags have date/time parameters, for these I had previously edited any ""hh" into "HH", any "mm" into "MM", any "mmm" into "MMM" and any "mmmm" into "MMMM" in line with the recommendations I had some years ago put in [[Webtags#List_of_allowed_modifiers|this table]] for Cumulus 1. That left "nn" for minutes in Cumulus 1 where I could not change it to a MX equivalent "mm" which Cumulus 1 would have taken as month. So now I created a new version of the one PHP script that used "nn", changed it in the new script to "mm" and changed the reference in the MX '''Cumulus.ini''' to the old file to refer to the new file. Subsequently I realised all my "am/pm" references had to be changed to "t" so I edited my new file again. Then another edit as I had a number of Recent History tags defined all with Cumulus 1 time specifiers having to be changed to MX equivalents. Yes quite a lot of work here, despite being able to use the Search ... Replace option in Notepad++.
#**# I have a few files that are PHP scripts listed in this section written as Cumulus templates; each has a number of PHP variables being set equal to a Cumulus web tag. In some cases the web tags have date/time parameters, for these I had previously edited any ""hh" into "HH", any "mm" into "MM", any "mmm" into "MMM" and any "mmmm" into "MMMM" in line with the recommendations that I had some years ago typed into [[Webtags#List_of_allowed_modifiers|this table]] for Cumulus 1. That left "nn" for minutes in Cumulus 1 where I could not change it to a MX equivalent "mm" because Cumulus 1 would have taken as month. So now I created a new version of my one PHP script that used "nn", changed it in the new script to "mm" and changed the reference in the MX '''Cumulus.ini''' to the old file to refer to the new file. Subsequently I realised all my "am/pm" references had to be changed to "t" so I edited my new file again. Then another edit as in the same file I had a number of Recent History tags defined all with Cumulus 1 time specifiers having to be changed to MX equivalents (although I don't believe I use them from this script anywhere). Yes quite a lot of work here, despite being able to use the Search ... Replace option in Notepad++.
#**# I also have some of my web pages generated from my own Cumulus templates. All the web tags in these that use date-time specifiers had to be edited, because I want to still use Cumulus 1 until MX is doing all I want, all these templates were given new names and I had to adjust the entries in "Cumulus.ini" to use these new names.
#**# I also have some of my web pages generated from my own Cumulus templates. All the web tags in these that use date-time specifiers had to be edited, because I want to still use Cumulus 1 until MX is doing all I want, all these templates were given new names and I had to adjust the entries in "Cumulus.ini" to use these new names.
#**In the "'''[NOAA]'''" section I had '''MonthFileFormat="NOAAMO"MMMyyyy".txt"''' on a line, I checked at [[Webtags#List_of_allowed_modifiers|List of allowed date/time modifiers]] that 'MMM' and 'yyyy' were valid in Cumulus MX as well as in Cumulus 1, they were so no edit needed either to that line or to "YearFileFormat="NOAAYR"yyyy".txt" line.
#**In the "'''[NOAA]'''" section I had '''MonthFileFormat="NOAAMO"MMMyyyy".txt"''' on a line, I checked at [[Webtags#List_of_allowed_modifiers|List of allowed date/time modifiers]] that 'MMM' and 'yyyy' were valid in Cumulus MX as well as in Cumulus 1, they were so no edit needed either to that line or to "YearFileFormat="NOAAYR"yyyy".txt" line.
Line 103: Line 103:
  netsh http add urlacl url=http://*:8998/ user=\users
  netsh http add urlacl url=http://*:8998/ user=\users
to allow all users to bind to port 8998 (used for the Cumulus interface).
to allow all users to bind to port 8998 (used for the Cumulus interface).
# I now type "http://192.168.1.64:8998/" into my browser after starting the MX engine, and I see the user interface.


My exploration of Cumulus MX has succeeded, and the experiment did help me find a mistake in one of my Cumulus templates, so it has been useful.
I now type "http://192.168.1.64:8998/" into my browser after starting the MX engine, and I see the user interface.
 
My exploration of Cumulus MX has succeeded, and the experiment did help me find a mistake in one of my Cumulus templates where I had not defined input parameters for "Recent History", so it has been useful.


= Updating to a new MX release =
= Updating to a new MX release =
5,838

edits