"Also, you can think of the example.com folder in your FTP space as public_html for that domain."
I'm starting to get it, I think. This actually makes logical sense.
However, please accept my apologies, I come from a world where user directories are always /home/login and web files go into /home/login/public_html. There is another thread somewhere about using modrewrite to allow the use of public_html, but there is a great deal of noise about how "lame" example.com/~user2 is.
I'm unsure in the context of DH how to give user2 FTP access to a user-style directory that would be accessible via the web at www.example.com/~user2 instead of having to create user2.example.com.
I created the following symlink, but I'm not totally convinced this is the way DH would prefer that I accomplish this...? (It obviously would not work if user1 and user2 were on different hosts and NFS was not available.)
[jurupa]$ ln -s /home/user2/public_html \~user2
where users.example.com is already established via the web interface.
Does this query even make sense?
(For those who come along later, the \ (backslash) is important, because you need to escape the ~ character. Otherwise the shell assumes that ~user2 means "the home directory of user2")
Jack Bauer is the "i" in team