Tuesday 02 December 2008 8:36:07 am
We've been looking for a perfect Subversion setup for quite a while. I agree the speed issues you face should not be related to SVN. Our developers have different OS's and sometimes they work away from the office, so having a server environment for each developer was not very attractive. A solution shared by our friends in Commonplaces was this: Use a single development machine. Each developer has their home directory accessible through Samba. They check in/out accordingly from SVN. The dev server has virtual hosts that respond to each developer. eg. developer1.project.company.com.
This way you only have one server, one db, but multiple code working areas. When code is ready, developer check in, and the SVN admin approves the code to move into the official dev environment and eventually into production. The VirtualHost and siteaccess take a little time but can be reused. Just thought I'd share this. Regards, Felipe
Felipe Jaramillo
eZ Certified Extension Developer
http://www.aplyca.com | Bogotá, Colombia
|