CumulusUtils: Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search
2,099 bytes added ,  07:14, 14 April 2021
Line 52: Line 52:
                       [ [[SysInfo]] ] [ [[Forecast]] ] [ [[StationMap]] ] [ [[UserReports]] ]
                       [ [[SysInfo]] ] [ [[Forecast]] ] [ [[StationMap]] ] [ [[UserReports]] ]
                       [ [[pwsFWI]] ][ [[Records - Top10|Top10]] ][ [[Graphs]] ][ [[Yadr]] ][ [[Records]] ]
                       [ [[pwsFWI]] ][ [[Records - Top10|Top10]] ][ [[Graphs]] ][ [[Yadr]] ][ [[Records]] ]
                       [ [[NOAA]] ][ [[Records - DayRecords|DayRecords]] ][ [[AirQuality]] ][ [[ChartsCompiler|CompileOnly]] ]
                       [ [[NOAA]] ][ [[Records - DayRecords|DayRecords]] ][ [[AirQuality]] ][ [[UserAskedData]] ]
                      [ [[ChartsCompiler|CompileOnly]] ]
                       | [ [[Thrifty]] ] [[All]]
                       | [ [[Thrifty]] ] [[All]]
                       | [[CheckOnly]]
                       | [[CheckOnly]]
Line 66: Line 67:


Copying to the webroot can also be done automatically through the FTP account of the user, much like ''CumulusMX'' itself copies e.g. the realtime.txt or the datafiles to the webroot. The FTP account and domain used are the same as present in the [[Cumulus.ini]] configuration.
Copying to the webroot can also be done automatically through the FTP account of the user, much like ''CumulusMX'' itself copies e.g. the realtime.txt or the datafiles to the webroot. The FTP account and domain used are the same as present in the [[Cumulus.ini]] configuration.
=== When and why to run ===
Running CumulusUtils results in output which represents a static view of the data in a table or graphic format for display on your website (or even a complete website). The fact that the output is a static view requires the output to be regenerated when new data is available. Rerunning CumulusUtils is also required when you change anything in the configuration and can't wait to see that change reflected on the site. In general: changes in data and configuration require a rerun.
Reruns for changes of data are typically once  per day, just after rollover time. In that sense it is like running a new query.
There are some exceptions to the daily rule: Sysinfo and UserAskedData
#Sysinfo: a rerun with Sysinfo is required when you wish to update the system information which can be a requirement from every 10 minutes to once per day
#UserAskedData: provides data for charts which are otherwise not available. Again this is at a user desired frequency which is recommended to be the FTP frequency defined in Cumulus.ini (parameter ''UpdateInterval'' in section [FTP site])
==== RPi: Using crontab ====
Automating the run of CumulusUtils on the Raspberry Pi is typically done through [https://man7.org/linux/man-pages/man5/crontab.5.html ''crontab'']. Below is the crontab of the author of CumulusUtils to be used as an '''example'''!
  15 1 * * *  cd /home/CumulusMX; utils/bin/cumulusutils.exe thrifty website
 
  09 * * * *  cd /home/CumulusMX; utils/bin/cumulusutils.exe sysinfo UserAskedData
  19 * * * *  cd /home/CumulusMX; utils/bin/cumulusutils.exe sysinfo UserAskedData
  29 * * * *  cd /home/CumulusMX; utils/bin/cumulusutils.exe sysinfo UserAskedData
  39 * * * *  cd /home/CumulusMX; utils/bin/cumulusutils.exe sysinfo UserAskedData
  49 * * * *  cd /home/CumulusMX; utils/bin/cumulusutils.exe sysinfo UserAskedData
  59 * * * *  cd /home/CumulusMX; utils/bin/cumulusutils.exe sysinfo UserAskedData
 
  0 9 * * *    /home/cumubackup.sh > cumubackup.log 2>&1
==== Windows: Using the scheduler ====


== Additional remarks ==
== Additional remarks ==

Navigation menu