title: Mac Osx Yosemite localhost document path errors
body: <p>Working in Yosemite's localhost for a few months now. Previously I went through a simple configuration tutorial where the URL would be localhost/~username/project/public. Never really bothered me since I was just messing around with some simple sites. I recently ran into a problem with Laravel and Angular and its been suggested that my URL having the public in it was causing my routes to fail. </p>
  
  <p>So I edited /etc/apache2/extra/httpd-vhosts.conf with</p>
  
  <pre><code>&lt;VirtualHost *:80&gt;
      DocumentRoot "/Users/jeffcairoli/Sites/"
      ServerName localhost
  &lt;/VirtualHost&gt; 
  
  &lt;VirtualHost *:80&gt;
      DocumentRoot "/Users/jeffcairoli/Sites/time-tracker-2/public"
      ServerName time-tracker-2.local
      &lt;directory "/Users/jeffcairoli/Sites/time-tracker-2/public/"&gt;
          Options Indexes FollowSymLinks MultiViews
          AllowOverride All
          Order allow, deny
          Allow from all
      &lt;/directory&gt;
  &lt;/VirtualHost&gt;
  </code></pre>
  
  <p>In /etc/hosts I added:</p>
  
  <pre><code>127.0.0.1        localhost
  255.255.255.255  broadcasthost
  ::1              localhost
  fe80::1%lo0      localhost
  127.0.0.1        time-tracker-2.local
  </code></pre>
  
  <p>In /etc/apache2/http.conf I uncommented the virtual hosts and vhost loadmodule. </p>
  
  <p>When I visit time-tracker-2.com I am directed right to apache's It works! page.</p>
  
  <p>I cannot figure out what I need to change to actually get it to point into my projects public folder so my laravel routes will take over. If anyone has any pointers or a better way to get my urls working please let me know. This issue is starting to drive me nuts.</p>
  
  <p>**Update After making the changes to the vhosts and hosts files that I added here, I now get a 403 Forbidden when i visit localhost or time-tracker-2.local. localhost/~jeffcairoli brings me to the listing of all my files in my sites folder. Im not too sure if I am looking at this wrong or something. I've always had an issue getting these to work. Haven't been able to get any of the typical 403 fixes to work there but I think that tells me that at least its recognized my changes since the urls are actually giving me a response. </p>