May I suggest-request a more logical and efficient way of configuring virtual hosts in future versions of OLS, as to having a tree structure hierarchy between domains and their subsequent subdomains. This would greatly simplify VH configuration, creation/addition, maintenance and updates while only having to change settings in the top domain, which would propagate to all subdomains via automatic inheritance.
Example:
VH0: mydom.com
VH1: dev.mydom.com
VH2: doc.mydom.com
VH3: sub.doc.mydom.com
At this moment you'd have to configure all of them separately, each tab in the webadmin. Best you could hope for is copy-pasting each field of each tab from the top domain config. Once you have to update a setting however, you'll have to do it manually on not just the top domain but ALL subdomains.
ENTER: INHERITANCE - The Virtual Hosts listing would no longer be a list but becomes a tree view:
mydom.com
├―dev.mydom.com
╰―doc.mydom.com
╰―sub.doc.mydom.com
This way configuration is inherited per the hierarchy displayed, so only differences in the subdomains need be configured, if any. Otherwise all settings are inherited from the top-upper domain (Log settings, Security, Rewrites, Context, SSL, Modules...).
More so, this structure could be automatically determined by the directory structure as stored on the disk/storage.
The only down side of this would be a possible incompatibility with previous configurations of VHOSTS, however it could be ported when upgrading.
Example:
VH0: mydom.com
VH1: dev.mydom.com
VH2: doc.mydom.com
VH3: sub.doc.mydom.com
At this moment you'd have to configure all of them separately, each tab in the webadmin. Best you could hope for is copy-pasting each field of each tab from the top domain config. Once you have to update a setting however, you'll have to do it manually on not just the top domain but ALL subdomains.
ENTER: INHERITANCE - The Virtual Hosts listing would no longer be a list but becomes a tree view:
mydom.com
├―dev.mydom.com
╰―doc.mydom.com
╰―sub.doc.mydom.com
This way configuration is inherited per the hierarchy displayed, so only differences in the subdomains need be configured, if any. Otherwise all settings are inherited from the top-upper domain (Log settings, Security, Rewrites, Context, SSL, Modules...).
More so, this structure could be automatically determined by the directory structure as stored on the disk/storage.
The only down side of this would be a possible incompatibility with previous configurations of VHOSTS, however it could be ported when upgrading.
