title: Symfony project on CPanel account
body: <p>For a bit of history - this is the first time I attempted to setup a test symfony project, just to have a play with it.</p>
  
  <p>The symfony project was setup in the following location:</p>
  
  <pre><code>~/symfony_projects/myproject/
  </code></pre>
  
  <p>Now, with cpanel, the httpd.conf is automatically generated (but I'm sure you knew that), and it uses <code>~/public_html/</code> as the web root and splits it up by domain name (virtual hosts) - so for this example, lets say it's <code>~/public_html/example.com/</code>.</p>
  
  <p>So the symfony project is all setup now, the next problem was trying to figure out how to setup the server so it points to the <code>/web</code> part of the project - this is where I found it tricky.</p>
  
  <p>I tried doing the following:</p>
  
  <pre><code>ln -sf ~/public_html/libs/Symfony/data/web/sf ~/symfony_projects/myproject/web/sf
  ln -sf ~/symfony_projects/myproject/web/* ~/public_html/example.com
  </code></pre>
  
  <p>That unfortunately didn't work though. When trying to go to <a href="http://www.example.com" rel="nofollow">http://www.example.com</a> it just gave me a <code>500</code> error.</p>
  
  <p>Any other options here? Taking into consideration that I cannot modify the <code>httpd.conf</code>. And even if I could, it's auto-generated and would rather not (in cpanel).</p>
  
  <p><strong>* Update *</strong></p>
  
  <p>I just tried what was suggested by @Dan, but with the same issue - getting <code>HTTP Error 500 (Internal Server Error)</code>. So, it looks like something else is the issue.</p>
  
  <p>I checked my error_logs but didn't see anything useful there. Is there any other way I can check to see what the problem is?</p>
  
  <p><strong>* Another Update *</strong></p>
  
  <p>Just tried <code>http://example.com/frontend_dev.php</code> and it works perfectly - gives no errors at all, which makes it kind of hard to debug the production controller.</p>
  
  <p>So the Development controller works flawlessly and the production is spitting out the 500 error - any ideas? :/</p>