The process that I am/was using was to create a tag file that was output to the unix side kin of how markb is doing it, though it is more like php code.
I have a php script that would pick that up in real time and generate on the fly an XML file. It also provided documentation at the same time if you called the php script with options.
The XML side worked okay, but I was having strange results which I think are more due to the configuration that I have rather than the script itself.
Unfortunately, this has been a crushingly busy year... since before January, I've been absolutely swamped. About the only thing I've kept up on is request for the Cumulus User map which is easy since I can do that with my cell phone if needed. Economy may be bad, but it has not effected my business, never been so busy.
I will say that Cumulus has been rock solid
since I have basically not touched the workstation for long stretches of time without any real issues. The only problem is tha I've had to cull the realtime.log files from time to time which I do on the 5th of each month.
I am upgrading my server here shortly and might have some breathing room soon to do some more playing...
Current php output:
Used with an option ?desc it was a self-documented output
The tag file it reads is like this on the Cumulus side...
Code: Select all
$FIELDS = array (
'formatver' => array ( '1.2',
'NOT A TAG. This is the version of this configuration file.' ),
'version' => array ( '<#version>',
'The version of Cumulus in use' ) ,
'build' => array ( '<#build>', 'The build of Cumulus in use' ),
'generated' => array ( '<#shortdayname>, <#day> <#shortmonthname> <#year> <#hour>:<#minute> -0700', 'Generated Date' ) ,
'date' => array ( '<#date>', 'The current date.' ) ,
'time' => array ( '<#time>', 'The current date and time' ),
'hour' => array ( '<#hour>', 'The current hour as a 2-digit number.' ),
'minute' => array ( '<#minute>', 'The current minute as a 2-digit number.' ),
'day' => array ( '<#day>', 'The current day as a 2-digit number.' ),
'dayname' => array ( '<#dayname>', 'The current day as a word.' ),
'shortdayname' => array ( '<#shortdayname>', 'The current day as a shortened word' ),
'shortmonthname' => array ( '<#shortmonthname>', 'The current month as a shortened word.' ),
'month' => array ( '<#month>', 'The current month as a 2-digit number' ),
'monthname' => array ( '<#monthname>', 'The current month as a word.' ),
'year' => array ( '<#year>', 'The current year as a 4-digit number.' ),
'shortyear' => array ( '<#shortyear>', 'The current year as a 2-digit number.' ),
'stationtype' => array ( '<#stationtype>', 'The type of station in use' ),
'recordsbegandate' => array ( '<#recordsbegandate>', 'The date that the all time records began' ),
'graphperiod' => array ( '<#graphperiod>', 'The number of hours displayed by the graphs' ),
'rollovertime' => array ( '<#rollovertime>', 'Data Roll overtime as in Midnight or 9am' ),
'update' => array ( '<#update>', 'WThe date and time of the last web site update' ),
'location' => array ( '<#location>', 'The station location' ),
Which the cumulus-xml.php script parsed to do what it does...
When used in a script, you ended up with an array which had a unique id_name to reference them by which is how some of my scripts are working.