Was wondering if I could get some advice on setting up a good subversion
environment for our web software. Our deployment and version control
right now is a big headache, so I've been reading The Pragmatic
Programmers: Pragmatic Version Control Using Subversion book. Problem
I'm having with this book and other guides I've read is they all seem to
be geared towards stand-alone compiled applications. Having a hard time
translating that to a web environment where Apache, Database, etc come
into play and have very specialized setups that is difficult to
reproduce on a workstation.
For one piece of software we have been running subversion smoothly for
over a year now. It's a simple application that doesn't have any client
specific customizations, so we can just update release candidates. But
with our main application we provide heavy customization. We have Dev,
Test, and Live servers, which is working out just fine. Problems is
when we have 2 or 3 projects going on at the same time. All of them are
polished and on Test, but only two of them need to launch up to live.
So right now we keep track of every single file we change, then svn up
each one individually on the live server, to make sure nothing from the
3rd project is accidentally pushed.
I think this is a horribly inefficient approach that isn't utilizing the
huge advantage of version control. But without creating a massive mess
of branches or any other complications with will provide more room for
error, I'm not sure how to resolve it. Anybody know of a good SVN for
the Web guide? Or even just some recommendations from personal experiences?
Thanks in advance,
Eric Jensen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 8 22:25:19 2007