Setting /home/myaccount/webdev/site1 as the DocumentRoot would be the path of lease resistance. Else, aliasing /site1/ to /home/myaccount/webdev/site1 would be another alternative. -Andrew On Wed, Apr 4, 2012 at 11:19 AM, Olwe Bottorff <galanolwe at yahoo.com> wrote: > I followed the directions here ( > http://tuxtweaks.com/2009/07/how-to-configure-apache-linux/) to set up my > LAMP to go directly to my /home/myaccount/webdev web sites. For example, > from my browser I type in this address: http://site1 and it goes to > /home/myaccount/webdev/site1 and grabs the index.html file. This saves me > the work of putting everything in /var/www/ for Apache to serve it. Good. > All is working. > > So I try to access site1 on another computer on my home network (home > Wifi) and I'm able to get to the Apache "It Works!" file in /var/www/ with > this address: http://192.168.0.4 which is the address of the host > machine, but when I try http://192.168.0.4/site1 it cannot find it (Not > found). Any ideas how I can help my other home machines see my home > directory web sites? > > Olwe > GM,MN > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20120404/33f0e34d/attachment.html>