Following first installation of Virtualmin 3.78gpl, I created a virtual host for harbour-side.com. This yielded a default home directory of home/harbour-side and a user name of harbour-side.
When I attempted to create a virtual host for harbour-side.com, I received errors because Virtualmin appeared to want to use the same defaults. I was able to resolve this by using the "Change Domain Name Settings" page and renaming the first home directory.
After several days of use, and several updates (including a yum -y update) I needed another pair of domains added ( a .co.uk and a .com). This time however, I received no error. The first domain was given defaults that did not include the domain's TLD but the second one was given defaults with the TLD as in:
/home/freethinking (user name freethinking)
/home/freethinking.com (user name freethinking.com)
So, I am not sure whether I am reporting a bug (which I am, sort of) or making a feature request (which I am, certainly). If the defaults always included the TLD maybe the bug I am reporting just goes away!
Regards Mark
Comments
Submitted by JamieCameron on Thu, 06/17/2010 - 21:34 Comment #1
It sounds like you want to have Virtualmin always use the full domain name for the home directory..
This can be done at System Settings -> Module Config -> Defaults for new domains, by setting the "Home subdirectory" to
${DOM}Normally this isn't an issue, as the other domains are typically created as sub-servers of the .com domain, and so don't get their own directory under /home
Submitted by kevanharding on Fri, 06/18/2010 - 15:29 Comment #2
I have checked the setting for home directories under "Defaults for new domains". There is only one that could be set to the value of "full domain" that you refer to and it is set to "Username or first part of domain"; presumably this is the default since I had not been aware of this setting before.
It seems this isn't the explanation for the behaviour I have described. You now also mention that other domains are typically created as sub-servers of the .com domain. In the trials I have done, that has not happened, so in what sense is it "typical"? And it puzzles me why anyway, would I want a .co.uk domain for example to be a sub-server of its .com equivalent?
But that might be because of my shortcomings in not fully grasping your terminology. For example: others generally referred to muliple domain hosts as virtual hosts. This gives the easier to grasp concept that one server (i.e. computer) can normally serve multiple virtual hosts. Your term for virtual hosts seems to be virtual servers, making the environment in your terms then read that one server or computer can serve multiple virtual servers. Isn't that confusing things a tad to change the term and thus use the word server too much?
Same with sub-servers. Are they the same thing that most others call subdomains?
But, thank you for pointing me to the "Defaults for new domains" setting. This has addressed my original problem even though it might not address yours (yours being that the default setup can cause unecessary difficulties as it stands.
To conclude. I submit that the matter of terminology is important, most especially to anyone new to Virtualmin. If there are widely understood terms for things (like virtual hosts and subdomains) then why change them unless you have good reason? I'll leave you to put that question to yourselves about whether you have good reason.
Thank you for the product Virtualmin, and the answer to my initial issue.
Regards Mark
Submitted by JamieCameron on Fri, 06/18/2010 - 16:29 Comment #3
Virtualmin uses the term "sub-server" to mean a virtual server that is owned by an existing user. This is separate from a "sub-domain", which means a virtual server whose domain name is under another domain (like office.foo.com is under foo.com). It may be that a sub-domain is also a sub-server, but this isn't actually mandatory.
We use the term "virtual server" to refer to both sub-servers and "top-level servers". A top-level server is the primary one for a user, and is what determines the directory under /home and the initial username.
In your case, what you should do is :
Does that help?
Submitted by Issues on Fri, 07/02/2010 - 18:20 Comment #4
Automatically closed -- issue fixed for 2 weeks with no activity.