Bug 50437 - Support adding any number of VHosts to apache
Support adding any number of VHosts to apache
Status: NEW
Product: UCS
Classification: Unclassified
Component: Apache
UCS 4.4
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: Dirk Wiesenthal
UMC maintainers
:
Depends on:
Blocks: 45115 50445
  Show dependency treegraph
 
Reported: 2019-10-30 13:56 CET by Dirk Wiesenthal
Modified: 2020-07-13 10:50 CEST (History)
5 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Wiesenthal univentionstaff 2019-10-30 13:56:08 CET
We ship a very "Univention centric" configuration for Apache.

3rd party Apps may be included, but they need to run below a root url ("/myapp") and they have to work with the overall configuration from us (timeouts, logfiles, etc.)

We should add a new script that allows software (and admins!) to add virtual hosts to Apache easily.

Each config should come with a dedicated ServerName, so that apache can distinguish the request.

Further configuration of this vhost should be possible through a Include directive.

+++ This bug was initially created as a clone of Bug #45115 +++

We should think about making the app available via appid.domain (not only fqdn/app)