5,838
edits
MX Administrative Interface: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
m
Updated warning at top of page
m (→MySQL settings: add warning) |
m (Updated warning at top of page) |
||
|
<div style="background: LemonChiffon;padding:5px; margin:2px;">
[[File:Crystal Clear info.png|40px]] This
Appeal to contributors: Please work through all MX release announcements and work out all the many updates needed for each section.
For example recent releases have totally changed the content of all settings pages in the admin interface.
Consequently, the whole page may even need either a replacement (set of) page(s), splitting of this page into multiple pages, or just a redesign of this section, for more recent releases!
</div>
=Terminology=
When he worked on Cumulus 2 alpha builds, he needed to explain how the design of his new software was different, and he talked about it separating "engine" and "user interface". Basically, the engine read information from the weather station, calculated derivatives, and monitored extreme records. The user interface was a web server generated by the engine, here you could amend settings, and see those weather derivatives (the alpha Cumulus 2 never had ability to feed any information to an external web server).
Thus Steve Loft used the same terminology (engine and user interface) for his Cumulus 3 beta (also known as MX). When Mark Crossley took over development and brought MX out of beta, he added much more to the web server that the engine generated, and he talks about "the code" where Steve used "engine" and he uses "admin interface" for the enhanced collection of web pages generated by "the code" allowing you to do many administrative tasks like correcting log files (both data logs and extreme record logs).
=How to see and use the Admin Interface=
| |||
