Apache’s Virtual Host configuration is perfect for the job. I like to have all my sites both current and past projects running locally so that I can fix any bugs etc without having to work on live sites. I’m sure you could probably add the default Apache user to a group or some other Users / Groups / Permissions setting but for a development machine this solution works fine! Problem #2: An alternative to name-based virtual hosts avoiding netinfo / hosts files I eventually figured out that in Leopard Apache’s default user (file to use my user and group and then it worked fine. Solution to #1: Change the user that Apache webserver runs as I tried to get it working and just gave up for a while and used the standalone MAMP application in the mean time to get working because this had no problem pointing to my custom DocumentRoot location. The problem I encountered was that if I changed the DocumentRoot to point to my preferred location I got a ‘Forbidden – You don’t have permission to access / on this server’ message. My first problem was that I like to use a different location for the DocumentRoot configuration, I keep my site files in ‘Users/rickcurran/Documents/Client_Data’ located in my Documents folder in my user account rather than in the default ‘Library/Webserver/Documents’ location. Problem #1: Access denied using custom DocumentRoot Leopard runs Apache 2 by default but I had been running this on Tiger anyway rather than the default Apache 1.3. One thing I found that I couldn’t get running correctly was recreating my preferred Apache web server setup including Virtual Host configuration.
VIRTUALHOSTX INSTALLATION TUTORIAL INSTALL
I recently installed Leopard on my development machine by doing a completely fresh install in order to have a clean system.
0 kommentar(er)
