As a last bit of advice to anyone else with this problem, when you change 
apache's DocumentRoot, you (probably) also have to change the Directory 
section just below it to keep the two working together. In a localhost 
development system, like mine, the DocumentRoot and the Directory have to 
be the same, else, you'll get a '403 Permission denied to access' message. 
Just copy out the existing Directory spec and enter the same Windows path 
that is used for DocumentRoot.

On Friday, April 11, 2014 1:41:47 PM UTC-4, Michael Laird wrote:
> Andy,
> Thanks for your help.
> I got Apache working serving pages from C:/User/userName directories with 
> just a small edit to httpd/conf
> If others have the same problem, this apache docs page gets right to the 
> point about DocumentRoot
> thanks again,
> On Friday, April 11, 2014 2:13:03 AM UTC-4, Andy wrote:
>> On 10/04/2014 01:46, Michael Laird wrote: 
>> > Andy, 
>> > Thanks for your response. 
>> > Messing with Apache fills me with questions. 
>> > If I put  newProject in another new directory, do I have to call it 
>> htdocs 
>> You can call it anything as long a DocumentRoot points to it. 
>> > Can I have newProject and existingProject in the same new directory, 
>> > whether it is named htdocs or newDirectory 
>> > Are we talking about VirtualHosts here, and is this documentation right 
>> > - 
>> No, we're simply moving the place that Apache looks for HTML files. 
>> You *can* set up Apache so that you have virtualhosts and each has a 
>> different DocumentRoot, but this isn't necessary for the problem that 
>> you reported - being unable to write into the current htdocs folder 
>> because it is within the 'Programs' hierarchy. 
>> -- 
>> Andy 

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to