[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Repository Set up Question

From: Joseph Koenig <joe_at_creativeanvil.com>
Date: 2007-11-06 04:16:31 CET

I'm wondering how everyone else has their development / test environment
set up. We're doing LAMP type development work, with all of the
developers working on Mac OS X workstations. We've got a CentOS 5
development server that is used for testing. I'm not a huge fan of the
way that each workstation has to have Apache and PHP installed in order
to work locally. It seems difficult to ensure everyone has the same
version of everything, same extensions, etc...

So, here's my ideal world situation of what would happen...

Each developer would have a network drive - through NFS or Samba. This
drive would be on the development server itself. Through ZendStudio, the
developers would checkout a copy of the project to their network drive.
So, essentially, it would just checkout a copy to their specific
workspace on the CentOS server. Apache would be setup with each
developer having their own workspace, for example, /www/userName1,
/www/userName2, etc. The httpd.conf file would simply allow them to
create userName1.domainname.com, etc. Then, when done working, they
would just commit their files back to the repository. This would ensure
everyone was using the same version of Apache, PHP, etc.

Has anyone else done anything like this? If so, any tips? Is this a
crazy idea?

Any help would be appreciated. Just trying to understand what everyone
else has done and what the downside of the above method would be...

Thanks!

-- 
*Joe Koenig*
*Creative Anvil, Inc.*
*Phone: *314.773.2611
*Fax: *314.773.2942
joe@creativeanvil.com
http://www.creativeanvil.com
Received on Tue Nov 6 04:17:20 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.