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? -Ian On 4/16/07, Diez B. Roggisch <[EMAIL PROTECTED]> wrote: > > > (I have found that is is easier to make the app rather than > > distributing it, thats a pity i think. Packaging and Distributing > > should be first priority for TG community if we want TurboGears to > > expand and to be massified) > > I don't share your obsevrations here. Packaging and deployment is considerably > easy with TG due to the heavy use of setuptools. Create the egg, transfer it > to the server, and invoke easy_install. > > And usually, TG applications don't get distributed the way you seem to want > it - normally, one installs a webserver, a python distribution and so forth, > setting up the whole environment. Then deploys the app. > > 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 -~----------~----~----~----~------~----~------~--~---
