ServerAlias and specific options for VHosts - manual configuration

[jmeyerdo]

Hi!

raphael Wrote:I think we should better populate some dir like /etc/ispcp/apache/custom so even subdomains and aliases have thir own, custom, .conf file.

Hmm, why not keeping all .conf-files for the apache at the same place?
So I would prefer "...../sites-available/domain.de" or "...../sites-available/alias.de".

Why should "/etc/ispcp/apache/custom/domain.de", "/etc/ispcp/apache/custom/alias.de", ... be better?

Kind regards, Jens

[raphael]

because files under sites-available are only available configs, nothing enabled.
An administrator would expect a2ensite domain.tld to enable the custom config, and since that wouldn't be the case, sites-available won't be used (neither sites-enabled becuase of the same reason: a2dissite).

[Cube]

I prefer joximu's proposal

Quote:/etc/apache2/ispcp/..

[jmeyerdo]

Hi!

Ok, I included the whole "sites-available" directory with my configuration because with CentOS "a2ensite" and "a2dissite" are not available.

For me it is not really important where to store the configuration-files. Of course I would like to see this feature in one of the next releases.

Have a nice day, kind regards, Jens

[joximu]

the "sites-enabled/available" folders are used in debian (and similar) distros.
suse uses "vhosts" and other distros maybe to.
So, it maybe easier to look for a solution which runs on every distro without much configuration...

That's what my proposal stands for

/J

[jmeyerdo]

joximu Wrote:So, it maybe easier to look for a solution which runs on every distro without much configuration...

That's what my proposal stands for

Ah, yes - of course!

Sorry, I used my (absolute) paths as example. But in my piece of code you can see that I used the configuration-variable: "APACHE_SITES_DIR". For me this is actually "/etc/httpd/conf.d/sites-available" but can be different with other distros.
So it is still my opinion that this APACHE_SITES_DIR is the best place for this - and not including .conf-files from different places.

Kind regards, Jens

[joximu]

But there are distributions which use a2ensite and asdissite (and other a2-commmands) to enable/disable apache sites (and mods) - suse, centos and others don't uise theese commands.
So, for non-debian distros conf.d (oder vhosts.d) is a good places to put the ispcp-domain.conf files but it's not the best place for debian based distros...

we have to find the best for all possible (or at least major) distributions...

Joxi