The time when application versions where stored in different folders or in zip files has ended. Today we have great tools like Subversion or CVS. This tools must be known by everybody, but for those who aren't known, they are applications that control versions of files.
While developing a Ruby on Rails application it's good to use a system like Subversion. In this howto I'll explain my experience subversioning my Rails app.
The first step is to create a subversion repository. Mine is created with a web interface in my hosting account, if you can control your subversion repositories and you don't know how to create it the chapter Creating and Configuring your Repository from SVN book may be useful. My repository url is (for example) http://someaccount.somehosting/myapp.
For subversioning a rails app we need, of course, a rails app. We'll create a dummy app for testing. After that we have to import this directory structure to our repository
The next actions have to be done in a working copy, the directory demo is no longer necessary.
After obtaining the working copy we have to prepare our repository for developers usage. The steps are:
Removing temp files
Removing log files
To remove these files doesn't mean "they are unnecessary", only means "there is unnecessary for these files to stay in the repo" :-).
To end up, the only final step is not subversion the config for accessing the database.