Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dev.icinga.com #6490] enable classic gui package to run in parallel with icinga1.x #1693

Closed
icinga-migration opened this issue Jun 15, 2014 · 2 comments
Labels
area/setup Installation, systemd, sample files enhancement New feature or request

Comments

@icinga-migration
Copy link

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

@icinga-migration
Copy link
Author

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).

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2014-11-11 22:45:52 +00:00

  • Status changed from New to Rejected

@icinga-migration icinga-migration added enhancement New feature or request area/setup Installation, systemd, sample files labels Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/setup Installation, systemd, sample files enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant