5,838
edits
MX on Linux: Difference between revisions
m
→Configuration files: Clarifying use of interface versus editing .ini file directly
m (→Configuration files: Clarifying use of interface versus editing .ini file directly) |
|||
|
The two examples above are in same folder as Cumulus.exe or CumulusMX.exe. You also may have configuration files in a '''mqtt''' folder, or elsewhere (for example I store some batch files that Cumulus runs for me in a batch folder).
If you have not used Cumulus before, there is useful guidance in various other articles that is not repeated here (it may seem a lot to read, but reading these instructions my save you from days of issues, just look at the support forum for examples of people struggling because they did not read up first and so missed key settings):
*To learn about what MX can do, please see [[About Cumulus]] article
*To learn about configuration, please see [[MX Administrative Interface]] and [[Cumulus.ini]] articles.
** It is important to see that whilst most settings can be done in the former, a few are read-only and must be done in latter
**Also note that some settings are related (e.g. you need to enable real-time before any real-time actions can be selected; equally you need to enable moon image generation before you can tick the upload option; these are just the 2 most common errors)
*For general advice relating to [[Cumulus MX]], follow that link
*For [[What to do when I have a problem with MX]], follow that link
*An article that needs someone to spend a lot of time improving it is [[Cumulus MX FAQ]], but the article could be useful
**The cumulus 1 [[FAQ]] might help (e.g. how to upload past data), but use with caution as Cumulus 1 and MX are very different in how they do many actions
Remember as mentioned earlier, the configuration file may need editing to update port names, any command locations, and to update file locations. Whilst you will find using the admin interface is easiest because it (in many cases) limits the selections to those that are valid; editing the Cumulus.ini file directly might be easier if you have moved from Windows and want to do repeat edits (e.g. changing multiple paths for files is easier using a repeat edit, that wading through all options in the interface).
*There is advice about port names at [[Cumulus.ini#Swapping_from_Cumulus_1_to_MX]].
*For '''Extra Web Files''', local file names will look like ''/home/pi/CumulusMX/web/trendsT.htm'' or '''/home/pi/cumulus_Templates/valuesRecentForDetailT.js'''.
**''Please note'' that Cumulus MX does not recognise "'''~/'''" as shorthand for '''/home/pi/'''.
**Your remote file names, if you have a local server as set up in the notes here, will look like ''/var/www/html/weather/trends.html'' or '''/var/www/html/weather/js/valuesRecentForTrends.js''', depending on your folder structure.
**Remember, MX needs full '''rw''' permissions to the HTML folder on your web site, if web site is on your Pi, then give permissions recursively using <tt>sudo chmod -R ugo+rw /var/www/html</tt> for Cumulus MX to successfully copy there.
=== data and Reports files ===
| |||