On Apr 16, 2007, at 2:52 PM, 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've been using workingenv.py for all my deployments recently and never looked back :) Makes distribution very easy because you can distribute the whole workiengenv as "the" app and be sure that the correct versions, patched libraries etc. will be used. I also want to investigate in creating a script that generates a .deb package out of a workingenv which should enable easiest deployment. Alberto --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
