My webserver is configured using a directory/host heirachy.

/etc/httpd/websites/
|
+--domain1.com
| +---hosts/
| +---www.conf
|
etc.

I have 2 files which load all virtual hosts :

/etc/httpd/websites/domains.conf
/etc/httpd/websites/{domain}/hosts.conf

The reason for this is due to the ease of disabling hosts or complete domains just by remarking 1 line in either domains.conf or hosts.conf as i need to. The other good thing is that this main websites/ directory is checking in and out of SVN for change control making it easy when you want to revert only 1 site ({domain}.conf) not 1 file (httpd.conf) for all.

Now that I've explained my issue, I was wondering if virtualmin would support this type of structure or would keep to the single httpd.conf method of things.

I want to use virtualmin but having so many domains/hosts to copy back to a single file almost makes me pass out ;)

I also think this is an easy/clean method of deleting hosts/sites without effecting any other files should corruption occur.

Hey George,

I believe Virtualmin does have support for the hosts/ format of virtual host configuration, though I've never used it myself. It is the standard method of setting up hosts on some supported platforms...yep, the options are in the Apache module configuration. They're labeled "File or directory to add virtual servers to" and "Filename pattern for virtual servers". Looks like setting this to "hosts/" and "($DOM).com" will do the trick, or at least pretty close to it. I believe it uses the include directory feature rather than explicitly pulling in each domain configuration in a separate file, as I think your example is suggesting. But pretty similar, and you'd be able to use your existing hosts configuration files unmodified.

However, I should point out that part of the appeal of Virtualmin is that you don't really need to think about the configuration files too much anymore. But since it is still possible to perform configuration using vi (or one of those other text editors) or any other tool that is friendly to standard configuration file editing, we do try to stick to the standards of the OS on which it's running.