Hi Santiago
All the mentions of virtualenv and pip are good, but I want to throw in another suggestion that will make your life a lot easier when working in teams and lower the discrepancy between "development machine" and "live server": Vagrant [1]. In fact, we're now running *all* projects in vagrant vm's with automated provisioning. Adding a new coder to the team involves * Checking out the repository that contains ** the vagrant configuration file ** the requirements.txt ** the setup.py ** the provisioning recipes * running `vagrant up` And you'll have a complete mini server that runs exactly the same architecture on each team member's dev machine and server. Alen [1] http://vagrantup.com/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/nwExUXgJTx4J. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
