Cleans up how our JS initializes module javascript. Previously the `rendered` event only got fired upon page load if a module got loaded as well. This is now decoupled and `rendered` events fire for all containers and the entire layout upon page load. Notable changes: * A `load` event initializes modules and triggers `rendered` on `.container` and `#layout` elements * Module javascript (module.js) is still lazy loaded but with a `beforerender` event, not `rendered` * Previously `#layout` received a `rendered` event during bootstrapping, this is not the case anymore * Initial search value preservation now got its own handler `events.onRenderedMenu()` * Initial dashlet loading now git its own handler `events.loadDashlets()` |
||
---|---|---|
.github/ISSUE_TEMPLATE | ||
.puppet | ||
application | ||
bin | ||
doc | ||
etc | ||
library | ||
modules | ||
packages | ||
public | ||
test | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
.travis.yml | ||
AUTHORS | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
COPYING | ||
README.md | ||
RELEASE.md | ||
VERSION | ||
Vagrantfile | ||
icingaweb2.ruleset.xml | ||
phpcs.xml |
README.md
Icinga Web 2
About
Icinga Web 2 is the next generation open source monitoring web interface, framework and command-line interface developed by the Icinga Project, supporting Icinga 2, Icinga Core and any other monitoring backend compatible with the IDO database.
License
Icinga Web 2 and the Icinga Web 2 documentation are licensed under the terms of the GNU General Public License Version 2, you will find a copy of this license in the COPYING file included in the source package.
Installation
For installing Icinga Web 2 please check the installation chapter in the documentation.
Documentation
The documentation is located in the doc/ directory and also available on icinga.com/docs.
Support
Check the project website for status updates. Join the community channels for questions or ask an Icinga partner for professional support.
Contributing
There are many ways to contribute to Icinga -- whether it be sending patches, testing, reporting bugs, or reviewing and updating the documentation. Every contribution is appreciated!
Please continue reading in the contributing chapter.
Security Issues
For reporting security issues please visit this page.