You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assignee: (none)
Status: Rejected (closed on 2014-11-11 22:45:52 +00:00)
Target Version: (none)
Last Update: 2014-11-11 22:45:52 +00:00 (in Redmine)
currently, the existing icinga1-classic-gui together with icinga2-classicgui-config is used for icinga2 classic web gui. This prevents to install both, icinga1 and icinga2 gui to run on the same host. Maybe its possible to use at least optionally /icinga2 in urls for a clear separation of both versions
The text was updated successfully, but these errors were encountered:
Updated by mfriedrich on 2014-06-15 20:18:27 +00:00
Category changed from Configuration to Packages
Imho the Classic UI shouldn't be the default 2.x interface and therefore only be used if the users really want it. Once Icinga Web 2 is finally released, it shall be the default interface to be installed with Icinga 2 (Core).
This issue has been migrated from Redmine: https://dev.icinga.com/issues/6490
Created by Tommi on 2014-06-15 19:58:51 +00:00
Assignee: (none)
Status: Rejected (closed on 2014-11-11 22:45:52 +00:00)
Target Version: (none)
Last Update: 2014-11-11 22:45:52 +00:00 (in Redmine)
currently, the existing icinga1-classic-gui together with icinga2-classicgui-config is used for icinga2 classic web gui. This prevents to install both, icinga1 and icinga2 gui to run on the same host. Maybe its possible to use at least optionally /icinga2 in urls for a clear separation of both versions
The text was updated successfully, but these errors were encountered: