I use a simple bash script to create an "externals" directory containing any specific stuff I need for the app concerned at the relevant versions, then I use the PYTHONPATH env variable to make sure that when I start the turbogears app, it loads from the externals dir.
$ cat create_external #!/bin/bash # # Run from the main directory to create the external dir with the right deps # needs setuptools installed # mkdir external mkdir external/lib mkdir external/bin PYTHONPATH="external/lib" easy_install -d external/lib -s external/bin TurboGears==1.0.0 Routes lxml TurboMail $ cat start #!/bin/bash PYTHONPATH="external/lib" ./start-myproject.py I have everything in a subversion repo,so I can't comment on the moving from dev to production (I use independant trees and meld between them due to my own release requirements), but a straight copy should work so long as you remember to tell the start script to load the production version for supervisor. On Mar 2, 6:42 pm, "Fabian" <[EMAIL PROTECTED]> wrote: > Hi, > I'm closing in on being finished with my first test project and things have > gone quite well for a first. Now however comes the question of deployment. > From the amount of trouble mod_python seems to cause I'm leaning to > mod_rewrite on apache2. With supervisor2 to keep it running. The apache > server currently does some static sites and a php site. Now the nagging > issue here is that since there are a few more tg sites going to go on there > is how to make them use specific versions of various components. Ie, use tg > 1.0.1 so that later sites installed there can use lets say 1.5 without me > having to retest all the previous sites for any incompatibilites. Same goes > for sqlobject, turbokid, etc etc etc. Does simply specifying ["TurboGears == > 1.0.1", "TurboKid == 0.9.9" etc etc] in setup.py and then turning it into an > egg and easy installing it on the server make it use only those components? > > I've also read > this:http://thraxil.org/users/anders/posts/2006/09/13/TurboGears-Deploymen... > supervisord-and-workingenv-py/ > However it left me more confused than anything. If anyone knows how this > works would it be possible to have a short how-to with a bit more detail on > what to actually do in a tg context. How do i add this to my tg app and then > do i still need to make an egg etc. when moving from dev machine to the > production machine? There are a few commands at the bottom but they seem to > skip over things and dont make a terrible lot of sense to me. > > Any experiences, recommendations anyone can share? > > Thank you, > Fabian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
