On Monday 16 April 2007 14:52, Ian Wilson wrote: > Depending on what you call an "app". It seems that putting an entire > website smack in the middle of python's site-packages is pretty wierd. > Especially if you are doing any reading and writing to things on the > drive, like images for example. And then you have to put the cfg file > somewhere... its not clear where. maybe inside site-packages.. or > maybe in some /etc/ dir? > > I just started using workingenv.py and that seems to be more sensible. > As well as using supervisord/supervisorctl as described in: > > http://thraxil.org/users/anders/posts/2006/09/13/TurboGears-Deployment-with >-supervisord-and-workingenv-py/ > > Which is actually linked to from the TG docs in > http://docs.turbogears.org/1.0#recipes under deployment. > > but maybe i am still following outdated ideas... what is other > possibilities are there?
I wasn't aware of workingenv. so far. I have no trouble installing stuff in site-packages, but then I've got a dedicated server for my app. So any dependency issues didn't arise, which eliminates the workingenv.py-need. And the whole supervisord-stuff - certainly interesting. But there is that error-500-recipe from somewhere in place in my installation. I agree that these things are handy. I'm just not sure if it's the responsibility of TG to "package" things more nicely, which is what the OP was asking for. Diez --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
