You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the article Hosting multiple websites with Apache2:

#10 Re: dynamically configured mass virtual hosting Posted by cfry (128.2.xx.xx) on Fri 7 Jul 2006 at 12:35 I personally use both. I have the generic configuration for anyone who doesn't need anything special, then on top of that I add custom VirtualHost sections for anyone who needs more. The small difference is that the VirtualHost sections don't need to redefine DocumentRoot and ScriptAlias. Also, because of the generic Virtual Root and Alias settings, each VirtualHost can use ServerAlias to configure the same configuration settings for physically different websites. For example, the mailing lists for all of my domains are all simultaneously configured with: <VirtualHost *:80> ServerName lists.example.com ServerAlias lists.* RedirectMatch permanent ^/$ /mailman/listinfo RewriteEngine on RewriteRule ^/mailman(/.*)?$ /cgi-bin/mailman$1 [PT,L] </VirtualHost>

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account