NOTICE: Updating Logarr
last edited 27 FEB 19 by @seanvree
Configuration change:
If updating Logarr to version 4.5 from ANY previous version, you will need to re-create your config.php file in the /assets/config/ directory after updating to v 4.5. You can do this by renaming your old config.php file, copying the file config.sample-06jun18.php to config.php, and then edit the newly created config.php file with your values.
Two new configuration options have been added/changed to config.php:
-
"rftime" (changed) : Specifies how frequently (in milliseconds) the UI clock will synchronize time with the hosting webserver. Previously the digital clock would update only when an ajax call was made at the interval defined by this value. Logarr version later than 4.5 will now use browser time after initial page load, however, will "synchronize" the UI clock with the server's time at the interval defined by this value. This update drastically improves performance as ajax calls are not needed as frequently.
-
"max-lines" (added) : Default line limit for all logs
See the Wiki section "Initial Configuration" for more information: https://github.com/Monitorr/logarr/wiki/04-Logarr-Settings
Logarr 5.0 will soon be released in the mid-Feb 2020 timeframe. When this version is published, updating via the UI by clicking on “check for update” in the footer MAY FAIL.
Issue: Beginning with version 5.0 several core functions will change with respect to how Logarr stores and manages the user’s personalized settings. Prior to 5.0 settings are stored in the /assets/config/config.php file which required the user to manually edit to configure Logarr. We will migrate to an integrated web-based settings GUI which will be used to update the Logarr settings. These settings will be stored in individual .json files hosted on the webserver’s filesystem. Given this, the conversion feature MAY fail upon initial setup of Logarr 5.x.
Resolution: When upgrading to 5.0 from ANY previous version, it is highly recommended to remove your local repository, and re-clone from GitHub or Dockerhub to ensure you have a fully functional local repository moving beyond v5.0.
If you need help, please join us on DISCORD here:
