"Monitorr” is a self-hosted PHP web app that monitors the status of local and remote network services, websites, and applications.
a. This update is a MAJOR update to Monitorr with numerous fixes and enhancements. b. Docker image available here: https://hub.docker.com/r/monitorr/monitorr/
If updating to version 1.7 from ANY previous version, BEFORE updating backup your custom.css file located at: (Monitorr install path)/assets/data/css/custom.css . After the update is complete, simply restore the custom.css file to the same location overwriting the custom.css file that was updated. This is due to a bug which has been resolved in version 1.7, therefore, this process will no longer be needed in future updates. See the WiKi Update Notice for more information.
The following configuration changes need to be made AFTER updating to version 1.7.0 from ANY previous version. See the WiKi Update Notice for more information.
a. User Preferences:
b. Monitorr Settings: screenshot
c. Services Configuration:
a. This update is a MAJOR update to Monitorr with numerous fixes and enhancements. b. Docker image available here: https://hub.docker.com/r/monitorr/monitorr/
If updating to version 1.7 from ANY previous version, BEFORE updating backup your custom.css file located at: (Monitorr install path)/assets/data/css/custom.css . After the update is complete, simply restore the custom.css file to the same location overwriting the custom.css file that was updated. This is due to a bug which has been resolved in version 1.7, therefore, this process will no longer be needed in future updates. See the WiKi Update Notice for more information.
The following configuration changes need to be made AFTER updating to version 1.7.0 from ANY previous version. See the WiKi Update Notice for more information.
a. User Preferences:
b. Monitorr Settings: screenshot
c. Services Configuration:
This release is a HOTFIX for a bug was discovered in the Monitorr settings page form.
ISSUE: If a user clicks inside a field on any of the settings pages and fires ENTER keystroke, the ajax call will write blank data to the user's .json files in their data directory thus completely breaking Monitorr if the UI is refreshed and the blank data is loaded into the DOM.
See https://github.com/Monitorr/Monitorr/issues/167 for further details.
This release is a HOTFIX for a bug was discovered in the Monitorr settings page form.
ISSUE: If a user clicks inside a field on any of the settings pages and fires ENTER keystroke, the ajax call will write blank data to the user's .json files in their data directory thus completely breaking Monitorr if the UI is refreshed and the blank data is loaded into the DOM.
See https://github.com/Monitorr/Monitorr/issues/167 for further details.
Changelog:
NOTE: There are a lot of CSS changes. Please ensure to clear your browser's cache after updating.
Docker image is available via Dockerhub with "latest" or "develop" tags: https://hub.docker.com/r/monitorr/monitorr/tags/
Alert: Configuration change:
See Wiki for further details: https://github.com/Monitorr/Monitorr/wiki/NOTICE:-Updating-Monitorr
Starting with version 1.5.2 we added the feature to enable hot-links on the main Monitorr page for both "Standard" and "Ping only" check types:
If you are updating from any version prior to version 1.5.2, you will need to make a small change in your Monitorr settings. After updating proceed to the Monitorr Settings page "Services Configuration", you will notice that the new "Link Enabled" drop-down menu will be enabled for all your services. However, there will be no input field for your link to the right. Simply change the "Link Enabled" option to "No", then immediately to "Yes" again. If you previously had a link associated with that services it will appear in the input field. Do this with ALL your services FIRST before clicking "submit". IF you do NOT want a link associated with that service, change the option to NO.
Note2:
Users can/should place their custom images in the /assets/data/usrimg directory. If using docker: /app/images. This is especially important for Docker users as that directory will NOT be erased when re-building the container.
Changelog:
Docker image is available via Dockerhub with the "develop" tag: https://hub.docker.com/r/monitorr/monitorr/tags/
Alert: Configuration change:
See Wiki for further details: https://github.com/Monitorr/Monitorr/wiki/NOTICE:-Updating-Monitorr
Starting with version 1.5.2 we added the feature to enable hot-links on the main Monitorr page for both "Standard" and "Ping only" check types:
If you are updating from any version prior to version 1.5.2, you will need to make a small change in your Monitorr settings. After updating proceed to the Monitorr Settings page "Services Configuration", you will notice that the new "Link Enabled" drop-down menu will be enabled for all your services. However, there will be no input field for your link to the right. Simply change the "Link Enabled" option to "No", then immediately to "Yes" again. If you previously had a link associated with that services it will appear in the input field. Do this with ALL your services FIRST before clicking "submit". IF you do NOT want a link associated with that service, change the option to NO.
Note2:
Users can/should place their custom images in the /assets/data/usrimg directory. If using docker: /app/images. This is especially important for Docker users as that directory will NOT be erased when re-building the container.
Changelog:
Docker image is available via Dockerhub with the "latest" tag: https://hub.docker.com/r/monitorr/monitorr/tags/
Monitorr 1.0!!!
Docker can be downloaded here: https://hub.docker.com/r/monitorr/monitorr/
NOTE1: If you are updating to any version prior to 1.0 updating via the UI by clicking on “check for update” in the footer MAY FAIL. It is recommended to clone a new copy of this repo starting with version 1.0. Please See WIKI
NOTE2: After updating PLEASE clear your browser cache.
We thank you for helping us develop.
Cheers to the future.
Change log:
Added notice to footer:
NOTICE (16 MAR 2018): Monitorr 1.0 will be released ~18 March 2018. When this release is published, updating via the UI by clicking on “check for update” in the footer MAY FAIL. Please See WIKI for further explanation.
Added notice to footer:
NOTICE (16 MAR 2018): Monitorr 1.0 will be released ~18 March 2018. When this release is published, updating via the UI by clicking on “check for update” in the footer MAY FAIL. Please See WIKI for further explanation.