Instructions for Getting Started with Subversion on RIAForge using Subclipse
Start by following Brians instructions on getting started with Subclipse.
Before checking out your first working copy, you’ll need to create some folders and import the files for your repository. Start by connecting to your repository (e.g. http://svn.riaforge.org/lightwire). Then right click on the repository, new, new remote folder and create folders for branches, tags and trunk. Under trunk, create a folder with the name of your project.
Once you’ve done that, right click on the project named folder in subclipse (for me it was trunk/lightwire) and select import. Select the folder on your hard drive to import from which contains all of the files for the project and click “finish” and you’re done.
You can now go on to check out a working copy as in Brians instructions. If you have any questions, there is a good online book and Simeon always has a bunch of great Subversion postings that are worth checking out. Just search his blog for Subversion.


Thanks for the comment! The project folder under the trunk folder is definitely optional. I'm going to keep mine for now, but you're right, with a dedicated repo it isn't needed.
I'm kinda a newbie when it comes to version control systems. I'd like to know the difference between CVS and SVN and which is better.
I have a couple of resources I could use for getting started with CVS (like TortoiseCVS), but which resource can you advise me to get started with SVN, as a newbie.
I'm probably the worst person to ask as I know very little about source control. But from my understanding, SVN was put together by ex-members of the CVS team and was designed to overcome perceived shortcomings in CVS.
There is TortoiseSVN for accessing subversion repositories using a Windows computer, or you could use Subclipse - a plug in for Eclipse.
There are lots of articles online, so beyond the above advice, I'd try Googling!
There are a few differences between them, but among the most important, at least to me:
SVN directories, renames, deleted, and meta-data are versioned, allowing you keep track of structural changes.
SVN commits an entire batch with the same revision number.
SVN allows external repositories to be included/linked into your.
SVN has a much better delta algorithm for storing binary files.
SVN has better support of tagging and branching.
I've blogged about svn clients and servers a little, you can read it here: http://www.robgonda.com/blog/index.cfm/Subversion
Cheers.
Please let me know if this is not a bad choice, your comments and further recommendations are welcomed. Thanks guys.
Best Wishes,
Peter
OK, this is the scenario. Most of the projects I work on (ColdFusion, Flash, Flex etc), are done on my own. My current practice of back-up has always been to make copies of my projects and store them in a dedicated hard drive (don't laugh), as I work. For web-based projects, I would upload the files to the remote server. And it is always hell trying to sync the files on the remote web host and that on my local machine.
In essence I have 2 very important needs. One, to able to have version control on the source codes of my projects. And Two, to be able to sync files I have on my local machine with teh ones deployed on remote web servers. Dreamweaver's built-in synchronize capabilities aren't that good enough for me, not to mention how long it takes over my modem internet connection.
Basically, these are the problems I faced with, and I'd sincerely appreciate your advice (which could include which software, tools, cvs or subversion etc) on how I can tackle them.
Thanks