> Once I delete prod.cfg, it runs fine. This is weird - which > > configuration does tg_fastcgi.fcgi use ? Its source code say > > prod.cfg ! > > What happens when prod.cfg isn't found ? Is there a fall-back to > > dev.cfg ? This can explain things, if prod.cfg is somehow unsuitable > > for Bluehost. > > Look at the code in the commands.py module of your project. The comments > explain very detailed how the config file is searched & loaded. > > In a production environment, you should always give the path of the > config file as an argument to the start script, this ensures that this > config file, and no other, is loaded. >
It appears that when the given config name isn't found, dev.cfg is searched. I tracked the problem down to specification of: server.webpath in the configuration. Whenever I specify it, my application always returns 404. If I don't, it works fine. I think there's some bad interaction going on between server.webpath and the virtual path filter of CherryPy as specified in the tg_fastcgi.fcgi bridge. Did anyone have experience with it ? The problem is that I don't run the application from the domain root, but still want to make it work with nice URLs. Thanks Eli --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
