One problem with doing it this way is that your web files must reside in /Library/WebServer/Documents. This makes it tougher to get to and from these documents, compared to setting up a separate account for each web client, and having all client files in that account.

I prefer to use VirtualHostX from clickontyler.com. It's only $9, it handles all the config files for you, and allows you easily to point to any folder you want for your virtual host.

---
--
Greg Raven
Apple Valley, CA

[ Reply to This | # ]

You do have to be careful about /Library/Webserver/Documents since upgrading OS X, for example, will clobber whatever files you put in there. My solution is just to move the Documents to Documents-Apple Junk then add a symlink to my ~/Sites folder using ln -s. Actually, I have a couple sites that I administer, so what I do is symlink to ~/Sites/localhost, and "localhost" itself is a symlink to either ~/Sites/site1 or ~/Sites/site2, etc. depending on what I'm working on testing today. That way you don't need to sudo in order to change your localhosting directory.

[ Reply to This | # ]