On 12/5/06, iain duncan <[EMAIL PROTECTED]> wrote: > > > > 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. > > Thanks Jeff. I'll try all that out and report back. Now why wouldn't you > want to use autoreload in production? Is autoreload just Cherrypy's > autorestart on file save? ( that would make sense then I suppose. )
I am quite new to TG and the autoreload advice came from the IRC not personal experience. If it is correct, which I am currently assuming, experience tells me their would be a performance penalty since autoreload has to monitor file date/times to try and tell if needs to reload a module. This would require extra disk accesses, hence the performance penalty. Since I haven't used it in production yet, nor read the code to fully understand autoreload this is a Wild A$$ Guess (WAG) and my statement should be viewed with suspicion.<g> Maybe someone with more concrete knowledge about autoreload will jump in and add to the conversation. > Gotta say, I am not a fan of CherryPy's habit of killing itself on > errors though. I'd much rather see an error message printed and the damn > thing keep trucking. :/ My plan is to run it through mod_python for production. I haven't tried it yet though so I can't comment with any authority about it vs other methods. > Iain > > > > > > > -- Jeff Hinrichs Dundee Media & Technology, Inc j --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
