If you merely changed the document root of a website, why would you need to restart BIND? Moving the home directory of a virtual server to an existing directory is a rather bad idea, that’s probably why it doesn’t work in that form your screenshot shows.
the screenshot just showed where i guessed (incorrectly) i might have been able to make such a change.
my hope is to figure out if virtualmin allows me to change the root directory to an existing directory of another virtual-server. remember, this is entirely for multi-user-wordpress. i need to have all the functionality of “alias” but have the email options as well.
when i make manual changes to httpd.conf, i assume that i need to restart bind every time.
Locutus - let me apologize for all these questions today and thank you once again for your help!
Don’t mix up “home directory” and “Apache document root”!
The home directory is the actual Linux user’s home, and contains much more than just the public_html Apache root. If you put the home directory of one virtual server into the same directory as another one, you’ll create a major mess. Try to have two independent parties at the same house, simultaneously, and you’ll see what I mean.
And no, you don’t need to restart BIND when you make changes to Apache. To continue the analogies, just like you don’t need to wash your car when you have dirty dishes.
ok let me start over (and again i apologize for asking all these pesky questions)
If you put the home directory of one virtual server into the same directory as another one, you'll create a major mess.
i created a virtual-server, and now i wish to “redirect” ONLY where the website stuff lives. nothing else, except for the website stuff (not the home directory)
Don't mix up "home directory" and "Apache document root"!
ok we are not doing any of the home directory stuff, only the references from httpd.conf to anything having to do with the website.
i go into http.conf and change any directory reference from the new server [NEWserver] to the old server [OLDserver] (case thrown in for readability)
It might seem “odd” to do manual changes to the Apache configuration, but that’s indeed what is required in this case. Changing DocumentRoot, ScriptAlias and Directory to the desired new place is all okay.
To have that automatically done with new domains you create, you can make a special Template for that case and adjust the directives in the “Apache Website” section.
The combination of features you’re using there IS a bit unusual, yep, that’s why Virtualmin doesn’t have an out-of-the-box switch for it. Normally you’d use Alias servers for your purpose, which you can’t since you want individual real email accounts. Therefore you need full servers, and have to do manual adjustments to the template to achieve your goal.
Virtualmin is very flexible, but it cannot directly support ALL possible use cases. In unusual cases you have nearly full control using templates though.
