> This condition seems to be caused by a lack of a dev.cfg when TG is > looking for it. TG decides to use dev.cfg or prod.cfg based on > whether or not it can find setup.py. setup.py exists in your dev > directory and so does dev.cfg -- but in your deployment, setup.py > still exists but there isn't a dev.cfg. Could you test this out: Go > to your deployment directory, rename setup.py to setup.py-bak and then > try and start your app. > > Please post back to the list with your results.
Ok, I do indeed have to either: - call the start script with prod.cfg as a command line option - delete setup.py Further, while removing setup.py works iff the cgi script is being called from within the project directory, it was still failing if I switched to a different directory with the same autoreload message. The only way I have managed to make the cgi script work when called from wherever is to have this in my cgi: os.system( 'python /home/cliffhanger/Credit/start-credit.py /home/cliffhanger/Credit/prod.cfg') Now am I doing something wrong or does this means the docs on the cgi hack just do not work as they are on Ubuntu? Been a bit of a headache getting CherryPy to stay up, but considering how easily it goes down on an unfound bug ... I would think it will frequently be an issue that people are deploying with less than full control over where and how they get to use CGI. Thanks for the tips Iain --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
