Hi!

Even if I started implementation of adding/generating ServerAliases by isp-CP-webinterface I found a much more easier workaround now.
My primary goal is to use real ServerAliases and add special httpd-options to specific VHosts.

With the following small changes you can add specific .conf-files for each VHost manually on the console (ServerAlias, further options like WebDAV...). For each VHost a new subdirectory is created and all .conf-files are parsed by include-command in the ispcp.conf.

Add to "ispcp-dmn-mngr" in part "dmn_add_httpd_file_data" the following lines:

Add to "dmn_entry.tpl" the following line before </VirtualHost>:

If you want you can add a deletion-routine for the directory of course and you have to consider if you need this for subdomains/aliases also.

Usage:
Add .conf-files in the specific directory, i.e. an alias.conf:

I see the following advantages/problems:
+ administrator can add ServerAlias manually - and they are not overwritten with a domain-update
+ no major changes necessary
- no automatic checks by isp-CP if a new domain is added manually as ServerAlias this way already

Is there some feedback about this "hack"?

Of course I am still considering to go ahead with my own hack to add a ServerAlias-option for isp-CP-webinterface but this will need major changes. Perhaps this is planned for a later version?

Kind regards, Jens

This post was last modified: 11-01-2007 10:06 PM by jmeyerdo.

Sounds interesting, I might add it in my next changeset

Sounds interesting, I might add it in my next changeset

Is your changeset your private version or the official release?

In second case please let me know if I can "beautify" this small addon furthermore (add deletion of directory when deleting domain, add support for aliases, ...).

Kind regards, Jens

This is the offical here on the site if you mean that.

Greez BeNe

... I was wondering, what is the difference between this and creating an other .conf file under sites-enabled with something like

?
Otherwise we'll have to polute some directory (can't be sites-enabled because they are automagically loaded, sites-available doesn't seem to be a good dir for them either, probably some dir under /etc/ispcp but that would cause problems when running apache chrooted)

/etc/apache2/ispcp/..

I've actually tough about /etc/ispcp/apache/custom/...

Hi!

Thank you for your interesting replies.

Are you sure that it is possible to duplicate the "<VirtualHost domain.tld:80>" to add more options? I will try this today.

Do I understand you correctly that you want to add one additional "custom-directory" for all option-files?
That should be possible and would need less/no changes in the daemon/template-files, correct?
You have to make sure to load this additional directory after the sites-available directory - and the administrator should use names like domain.tld.conf (but this is obvious).

Perhaps we can discuss this also based on your "future ideas" regarding the conf-structure for VHosts? On the feature list is the point: single .conf-files for every VHost. Have you any ideas about this already?

Kind regards, Jens

Hi!

I tried your suggestion now - but encountered problems.
I added an additional custom-directory and told the httpd to parse this after sites-available.

But how to declare the correct corresponding VirtualHost?
"<VirtualHost domain.tld:80>" is not possible - because the IP is registered at this part instead of the domainname.

I tried with the following - without success, too. The Aliases are not recognized.

So we have to keep my solution?

Kind regards, Jens

ok, thanks for the info.

So... the thing now is: what directory do we use? I think we should better populate some dir like /etc/ispcp/apache/custom so even subdomains and aliases have thir own, custom, .conf file.