Moving from VSS to SVN - with Web based Shared Working Copies
Date: Thu, 21 Aug 2008 11:03:13 +0100
We are just at the beginning of trying to move from VSS to SVN. We've got our shiny SVN server all set up and running, but now it's the practical changes that are causing us the headache. We're trying to figure out how to move from VSS to SVN from our existing setup.
Currently we develop web applications using a shared development server, so in VSS files are 'checked out' to a developer, edited directly on the DEV shared area, run there while developing and then checked in. Other developers can obviously see that those files are being changed so must avoid them.
If we move to SVN in this scenario, we have the obvious problem that you can't really have more than one person changing the shared working copy at once - it defeats the whole copy-modify-merge thing.
The obvious thing is to develop on a local working copy, however this has it's own headache - how on earth do you replicate a huge development server, the databases, application server configurations, interconnections with other systems, etc., for each developer on a standalone machine?
This must be an issue for anyone developing web based applications, so how do people deal with it out there? Any pointers, sites discussing this or anything at all would be great!
Our problem at the moment is the whole change to SVN seems insurmountable because of this, and it's difficult to see any incremental steps that we could take to get there. Clearly we can't take three months out of 'ordinary work', just to completely revamp our entire development process and environment, so we need to somehow manage this is smaller stages.
Any help gladly received!
The Robert Gordon University is the best modern university in the UK (The Times Good University Guide 2009)
The Robert Gordon University, a Scottish charity registered under charity number SCO 13781.
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
This is an archived mail posted to the Subversion Users mailing list.