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 |
| Severity: | Hard | Keywords: | |
| Cc: |
Description
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
/etc/apache2/sites-enabled/example.com.conf
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
Change History
comment:2 Changed 5 years ago by malte
- 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
comment:3 Changed 5 years ago by anonymous
http://a-zoloft-side-effects.associates-program.com Zoloft Side Effects http://a-generic-zoloft.associates-program.com Generic Zoloft
comment:4 Changed 4 years ago by joximu
Just remember: not all distributions make use of symlinks in the apache config (xxx-available, xxx-enabled). But I also support the use of one file per customer (or domain/subdomain/alias...)
comment:5 Changed 4 years ago by rats
- Severity set to Hard
- Milestone changed from ispCP ω 1.1.0 to Working
Yeah...good point...it's hard to manage a single file when you have thousand of domains.