userdir&vhost,subdomains

hilo

I am curious too user dir I know it is possible to serve user pages out
of there home.
This is interesting because it is below server and doc root so what shall
be done to allow this, symlinks?

Also vhosts say domain.com how can user.domain.com be done
I understand doing multiple hosts using same ip
but that requires dedicated names.

so basically how does one go about creating a subdomains



<IfModule mod_userdir.c>
UserDir /home/public_html
UserDir disabled root

</IfModule>

#
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
#
<Directory /home/*/public_html>
AllowOverride FileInfo AuthConfig Limit
Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
<Limit GET POST OPTIONS PROPFIND>
Order allow,deny
Allow from all
</Limit>
<LimitExcept GET POST OPTIONS PROPFIND>
Order deny,allow
Deny from all
</LimitExcept>
</Directory>


say I want to serve domain.com/~me/index
from /home/me/

also guessing that ~ means symlink?
how about * what's that shadowed?

thanks all lots of stuff
believe me have searched all places reading up justt need some advice

my brain has been racked dealing with mail servers damn sympatico
if anybody knows how to masquerade around there block
that would be great


=D

>>I know it is possible to serve user pages out of there home.

Yes it's possible technically, but in practice, nobody would do that. You need mod_alias to map dir outside of your docroot. However, Alias/AliasMatch must be specified in httpd.conf or its Include file, not .htaccess. For users under userdir, their priviledges ovbiously are limited (no access to httpd.conf), so it's a bad idea in practice.

>> symlinks?

Yes, you can use SymLinksIfOwnerMatch to do that. If the dir is not writable by the user, he or she can't create symlink in the first place. To do that, you need to make sure the target dir is writable by that user.

>> Also vhosts say domain.com how can user.domain.com be done

This must first be done via DNS. As long as user.domain.com resolves to the same IP, then Apache can be configured to serve different content for user.domain.com.

>> so basically how does one go about creating a subdomains

This is off-topic here. Since you are asking something relevant to your other questions, I will reply you anyway.
If you have limited users who want user.domain.com, just add multiple A record of user1.domain.com to point to the same IP as your default server's IP. Don't use cname.

>> UserDir /home/public_html

This is misconfigured and highly insecure based on the setting with your <Directory "/home/*/public_html"> block.

The translation of UserDir /home/public_html is:

/home/public_html/username/index.html
http://www.domain.com/~username/index.html

Insecure because:

/home/public_html/username/.bashrc is world accessible via browser at http://www.domain.com/~username/.bashrc

With UserDir public_html (default), it's assumed to be:

/home/username/public_html/index.html ->
http://www.domain.com/~username/index.html

>> say I want to serve domain.com/~me/index from /home/me/

You need to give better example. I have no way of knowing whether index is a file or dir.

>> also guessing that ~ means symlink?

Not at all. That's dedicated for userdir.

>> how about * what's that shadowed?

Wildcard.

Well thanks alot freebsd

will not even think about userdir anymore, was curious about it.

Thanx again