SVN "layout" for small team

Currently we have no SVN/Git/Mercurial setup at work. We're fully aware it's a bad situation, so we decided that since we're about to start a new major project, we would get at least a basic SVN setup going.

The problem is that none of us have any real experience of SVN in a team environment. I, myself have used SVN and Git for my own projects in which I am the single developer.

Because of this we're confused on the best setup to use for our new development structure - currently we have a development server bbtsrv02 in which all files are l开发者_如何学Pythonocated on, we edit them, then upload them as we go.

This needs to change, however we're not sure how this new setup could work. I guess we'd need a local copy of the files, but our server is configured specifically for our websites and then how would we test them in the same environment? From there, we'd commit to bbtsrv02

What do you suggest? Is this setup wrong from the start?

We recently made this change as well. For us we doubled our in-house FTP/Web Server to also serve our SVN via HTTP. With this set-up we are able to work on and contribute to the project while also on the road. Which is a very common occurrence for us. We have hooked up the SVN from there to Hudson to create a automatic build for testing in a VM before pushing onto the web-server.

We host our SVN repository on a utility development server which, among other things, also hosts our issue-tracking software, FTP server, various network shares and project documentation.

We develop primarily ASP.NET applications, so we develop locally using either the Visual Studio development server or the local IIS instance on our workstations, and then uploaded to a development IIS/SQL server.

It's an exceedingly simple setup, but it suits our needs. It is not externally accessible, so we need to be in the office or connected via VPN.