Ticket #86 (assigned enhancement)

Opened 2 years ago

Last modified 8 months ago

Separate Domain VirtualHost files

Reported by: anoopalias01@gmail.com Assigned to: malte (accepted)
Priority: feature Milestone: ispCP ω 1.1.0
Component: Backend (Engine) Version: ispCP ω 1.0.0 - DEV
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

Attachments

Change History

03/10/07 08:08:48 changed by sorin@buzau.ro

Yeah...good point...it's hard to manage a single file when you have thousand of domains.

04/12/07 00:32:33 changed 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.

07/07/07 03:23:09 changed by anonymous

01/12/08 10:43:52 changed 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...)

02/17/08 14:40:22 changed by rats

  • severity set to Hard.
  • milestone changed from ispCP ω 1.1.0 to Working.

02/23/08 17:36:40 changed by rats

  • milestone changed from Working to ispCP ω 1.1.0.

if a dist doensn`t use a symlink, we could just create them in our config dir /etc/ispcp and then link them to sites-available or vhost.d (gentoo)


Add/Change #86 (Separate Domain VirtualHost files)