Actually, it *is* how I deploy to production. It ensures that I have complete control of the versions of the packages used, not the system.
Usually, the system package manager is pretty good for most things. For this sort of situation, though, it can make problems. I avoid it. On Mon, Apr 9, 2012 at 10:58 PM, Craig Small <[email protected]> wrote: > On Mon, Apr 09, 2012 at 10:49:43PM +0200, Alessandro Molina wrote: > > I would suggest you to always use virtualenv for all your projects, > > you will avoid issues with version conflicts with every package or > > framework you use, not only TurboGears. > > Is that also how you run your production environments? I've got a > development virtualenv but still working out how best to deploy my > project; either as me deploying it or writing up some document to tell > others how to do it. > > - Craig > -- > Craig Small VK2XLZ http://enc.com.au/ csmall at : enc.com.au > Debian GNU/Linux http://www.debian.org/ csmall at : debian.org > GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 > > -- > 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. > > -- Michael J. Pedersen My Online Resume: http://www.icelus.org/ -- Google+ http://plus.ly/pedersen Google Talk: [email protected] -- Twitter: pedersentg -- 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.
