On 12/4/06, Karl Guertin <[EMAIL PROTECTED]> wrote: > > On 12/4/06, iain duncan <[EMAIL PROTECTED]> wrote: > > The above doesn't happen when I try to start it from the project > > directory. Any idea what I need to do to get that working? > > http://trac.turbogears.org/turbogears/ticket/1186 >
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. I belive this to be true because if I delete dev.cfg and start a project I get the same error. If I start the project and specify the prod.cfg it works as expected. The 3rd belief is from what I was told on IRC and that was you don't want to run autoreload in product -- so I think it is a bug. I invalidated the original report, because as it was written -- it was wrong. As I've just described it. rm/rename dev.cfg rm/rename setup.py try and start project -- boom try and start project (specify prod.cfg) -- boom put dev.cfg back try and start project -- boom try and start project (specify prod.cfg) -- boom restore setup.py try and start project -- golden try and start project (specify prod.cfg) -- golden at least that what happens on Ubuntu 6.10 w/ TG 1.0b2 and a quickstart project with the defaults selected. -Jeff --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
