On Sat, Jun 28, 2014 at 09:49:52PM -0600, Warren Block wrote: > I've just been setting this up, and had a question and a couple of notes. > > Originally, I just installed icinga2. The icinga2 port does not depend on > icinga, but appears to need it. Is this really a dependency, or are the > two ports meant to be separate?
Icinga 2 itself doesn't need a web interface to work. The Icinga 1 port includes the classic (cgi) web interface which can be used for Icinga 2, so it's not a hard dependency. When I find the time I'm going to create a new port for the classic web interface. > > The icinga.conf-sample does not appear to be installed anywhere by the > current port. It can be found in the staging directory, > stage/usr/local/share/examples/icinga/apache22/. It's installed by the Icinga 1 port. From pkg-plist: %%PORTEXAMPLES%%%%EXAMPLESDIR%%/apache22/icinga.conf-sample Maybe you have NO_PORTEXAMPLES set? > > The embedded documentation shown is for 1.11, and it's not clear whether > the Javascript client for icinga 2 is available, or whether it will make > the CGI interface unnecessary. Actually, given the config file, and both > versions installed, the older version might be the one that is running. I > have not experimented with it much yet. Yes, the classic web interface still links to the Icinga 1 docs. I think this should be fixed upstream, so I created a bug report. Apart from the Classic UI there are two other interfaces for Icinga. Icinga Web and Icinga Web 2.x. The former isn't too good and will be deprecated eventually. The latter is much more straight forward but isn't ready for production yet. > > Thank you for your work on this! Thanks for testing it. :)
pgpSIjRqmLUtj.pgp
Description: PGP signature
