DOH! Had stuffed up my config. It propel database connection for the production environment wasn't suitable on my dev machine. I suppose, I need to look more into making a more clever setup...
/Thomas On Sat, Oct 18, 2008 at 11:47 PM, Thomas Vestergaard <[EMAIL PROTECTED]> wrote: > Hi all, > > Alvaro's advice worked like a charm! Thanks. :D > So I got the project up and running nicely on Servage. Turned out that > the troubles was probable due to delay in propagations of rights on > log and cache folders. > > However, I have now gotten myself into another situation were I get an > "500 Internal Server Error". > But this time I only get it with the production controller while > everything is dandy in development mode... :( > (This is on my dev-box, not on Servage.) > > To get some more information on, what was going on, I changed the > settings in settings.yml for the prod environment to match the dev > mode. I figured, I would then either get the same results or some > useful information on what was going haywire. (I.e. log-file, web > debugging.) > To my frustration nothing of this happened. I still get the "500 > Internal Server Error" and no log-file is made. (And i have cleaned > out the cache - several times.) > > Any ideas on what I am doing wrong? > > Thanks, > Thomas > > > On Thu, Oct 16, 2008 at 5:04 PM, Pablo Godel <[EMAIL PROTECTED]> wrote: >> Hi Thomas, >> >> I think Alvaro's suggestion might help. If you still have problems you >> can take a look at our Symfony hosting offering, >> http://servergrove.com/symfonyhosting >> >> We have specialized symfony hosting support, let me know if you have >> any questions. >> >> Regards, >> Pablo >> >> On Thu, Oct 16, 2008 at 7:26 AM, Thomas Vestergaard <[EMAIL PROTECTED]> >> wrote: >>> >>> Hi all, >>> >>> Got my project up and running on my dev-machine and figured it was >>> time to share the progress with at couple of stakeholders. >>> So I wanted to deploy the project to my own account on Servage. I >>> followed the guidelines on [0], except that I just pointed the >>> subdomain to the Symfony web directory. >>> After having solved a few errors with caching, I am now stuck with a >>> 500 Internal Server error. >>> Now - that is not a hell of a lot of information to try and track down >>> the problem! I tried to look in logs, but none have been created. I >>> tried to access the development-frontend, but gets the cheeky message: >>> "You are not allowed to access this file. Check frontend_dev.php for >>> more information." >>> >>> As I am completely at loss to were to go from here, I would really >>> appreciate any pointers to how I can figure out the source of this >>> error. >>> >>> [0]: http://trac.symfony-project.org/wiki/InstallingSymfonyOnSharedHostNoSsh >>> >>> Thanks, >>> Thomas Vestergaard >>> >>> >>> >>> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
