Ticket #86 (assigned enhancement)
Separate Domain VirtualHost files
|Reported by:||anoopalias01@…||Owned by:||malte|
|Priority:||feature||Milestone:||ispCP ω 1.x.0|
|Component:||Backend (Engine)||Version:||ispCP ω nightly build|
Currently VHCS Omega uses a single flat file for the virtual hosts (/etc/apache2/sites-enabled/vhcs2.conf)
Wouldnt it be better to use individual configuration files for each domain. The apache2 configuration file pattern is designed like that.This way we can individually enable or disable a domain (suspending!) by the commands readily available within apache2 .
As an example. If we have a domain name example.com a config file for it will be created like /etc/apache2/sites-available/example.com.conf and once the status of this domain is OK ,a soft link for the file will be created
This way it is a lot easier to manage the individual configurations rather than dealing with a bulky flat file.
This method is used by the Interworx control panel,and i guess it is much better than a flat file
- Owner set to malte
- Status changed from new to assigned
- Version changed from VHCS 2.4.x to ispCP ω 1.0.0 - DEV
- Milestone changed from ispCP ω 1.0.0 - RC2 to ispCP ω 1.1.0
- Severity set to Hard
- Milestone changed from ispCP ω 1.1.0 to Working