Quote:
Originally Posted by glen.barber
This doesn't answer your 'My Solution' question, but I do something similar on a development machine. I use subversion to checkout from my code repository into /home/me/svn/site and create a symbolic link for apache to this location:
Code:
rm -rf /var/www && ln -s /var/www /home/me/svn/site
|
I actually considered using a link. I don't know why, but I just
assumed that apache wouldn't play well with a link.
Quote:
Originally Posted by glen.barber
I know it doesn't answer your real question, but maybe this solution is easier. *shrug*
|
Well, this could be a work around. The only problem/reason its a work around and
not a solution is because I actually have 24 GB of data inside my development folders on a couple computers. such a large development folder brings about two problems here:
- my dropbox account doesn't have that much of storage (nor would I want it syncing that stuff anyway)
- whenever running my login's "switch-server's-location" script, it would have to move the 24 GB of stuff out of /var/www just for the link to work.
I'll probably use link to redirect Apache just on a computer or two right now, but I'll still be searching for a more thorough solution. Thanks again, glen.barber, I appreciate the input.
Perhaps someone with a better understanding of Apache than me could explain to me "
Apache's http root isn't meant to be fiddled with"? and such an undertaking isn't for the inexperienced?
