Home
Emoncms is moving towards a modular structure, and therefore a number of functions are being removed from the main emoncms core files, and placed into their own repositories. Examples include 'Dashboard, App, Device, etc.
The result of this will be that if you make a new installation, or git pull from an existing installation, the modules will be removed from your installation. However, they can be easily installed (or re-installed) by following this guide, and git cloning the module into your Modules folder.
Please note: as all existing dashboard settings are stored in MYSQL, re-installing the dashboard module will restore your dashboards! - the settings are not deleted.
Paul - 6/1/2016
The emoncms logfile location has been moved from the emoncms installation directory to /var/log/
The reasons for this are;
- /var/log is the established location for logfiles, and where people expect them to be
- Logrotate will then be able to manage the emoncms log, rotating, and limiting it's size
- In low-write mode, /var/log is placed into tmpfs (RAM) and therefore emoncms logging can continue to run without disk-writes
However, the implications for existing emonbase users are; (does not apply to emonPi's)
Not in low-write mode
Emoncms is unable to create a logfile, only write to one, therefore it's necessary to create the logfile and set it's permissions in it's new location - just like what was done during the initial installation (only needs to be done once):
touch /var/log/emoncms.log && chmod 666 /var/log/emoncms.log
In low-write mode
Following a git update, it will be necessary to run an update script, to make a number of required changes:
cd /var/www/emoncms/scripts/logger/ && sudo chmod +x install.sh
sudo ./install.sh
Paul - 6/1/2016