New VirtualHost

[Scott DuBois]

On 07/17/2014 01:37 PM, my mail wrote:
> On 07/17/2014 02:10 PM, Scott DuBois wrote:
>> Hi All,
>>
>> Over the last few days I've been working on setting up a new VirtualHost
>> inside Kubuntu 14.04 and been having difficulty getting any results
>> outside of the /var/www directory.
>>
>> I've been playing around with LAMP stacks for a number of years as
>> simple development platforms for HTML, CSS and MySQL projects but as I'm
>> starting to learn Perl and thought I would set up CGI scripting to
>> /var/www which is working great then got a "wild hair" and thought I
>> would try setting up a new VirtualHost pointed to /srv for practice in
>> going through the motions of getting this to work but I'm still getting
>> permission errors.
>>
>> I did a2ensite which resolved just fine and chmod /srv to 755
>> recursively as well as insuring all the files below are executable. My
>> file inside /etc/apache2/sites-enabled (sym'd to sites-available) is set
>> as such:
>>
> 
> 
> [snip]
> 
> Sorry if you already did this, but did you reload Apache after enabling
> the new virtual host:  sudo service apache reload
> 
> 
> 
> 


As this was the last message in the thread, I just wanted to take this
moment and thank everyone who tried to help and let all those who
subscribe to the list know that I have finally solved the problem I was
trying for.

After reading the following article, it made sense that I was trying to
establish a second DocumentRoot and access as a separate server location
when what I really wanted to do was serve a website from a location
separate from /var/www/html being /srv/www. While not intentionally
trying to escape sudo to my webdocs, the concept was parallel to my goal.

After successfully establishing two separate VirtualHost documents, thus
being able to establish two separate addresses the documents could be
retrieved from, I was still unable to force feed from /srv/www. however,
after creating a link:

ln -sT /srv/www to /var/www/html/srv

webdocs(/srv/www) -----> DocumentRoot(/var/www/html) -----> Browser

This provided the results I was essentially looking for and as such, can
move projects outside sudo and organize as desired. Such a simple fix
once approached from a different perspective.

http://askubuntu.com/questions/46331/how-to-avoid-using-sudo-when-working-in-var-www

Thanks again to everyone who tried to help as each suggestion got me
closer to the solution. ;P

-- 
Scott DuBois
President EBLUG
BSIT Software Engineering
Freenode: Roguehorse