There is nothing worse than losing code that you have spent eons writing. RubyMine has some nice built-in tools to manage your version control systems including Subversion and GIT repositories.
Open your Progeny Rails project in RubyMine.
Depending on your OS, download and install Subversion and GIT as follows:
For the Mac OS, subversion is already installed on the Mac OS X versions.
Git can be installed by downloading the installer for your version of OS X. The images can be found at https://code.google.com/p/git-osx-installer/.
Follow the instructions for the installer.
For Windows, Subversion can be downloaded and installed by running the appropriate installer for your system from http://tortoisesvn.net/downloads.html.
Git can be installed through the installer http://msysgit.github.io/.
Follow the instructions for the installer.
For Linux OS, subversion can be installed by opening a terminal window and typing:
sudo apt-get install subversionGit can be installed by typing the following command in a terminal window:
sudo apt-get install git
Now that we have subversion and Git installed, we can tell RubyMine which version control system that we want to use for our project. Let's start with Git:
Navigate to VCS | Enable Version Control System...
This will bring up a little window that will let us choose which VCS to use for this particular project. We can have different VCSs for each project that we have in RubyMine, as shown in the following screenshot:
Select OK. This will initiate the Git system and automatically issue the command
git initon your project.Expand some folders. You will see that all of the files are now color coded in red. This means that the files are not yet under version control, so we need to add them to our local Git repository. This takes two steps: Adding the files and committing the files.
To add the entire project, click on the frame panel button at the bottom of the project called 9: Changes.
Click on the link Click to Browse which is next to Unversioned Files. A new window will open with a list of files in the project.
Select the top-level folder and hit the green + button on the left of this window. This will add all of the files and folders to the project under the Git staging system. As shown in the following screenshot, the project window will now show all the files with a green color, which means the files are added to the local Git repository, but they have not yet been committed:
Now all we need to do is commit the directory using the following steps:
Right-click on the
projectfolder in the project list and navigate to Git | Commit Folder. This will bring up a window like the following:
From this window, we can select many options, but the most important is to add a comment in the bottom text box. This comment will follow this commit forever.
Type
Initial Project Commitin this box.Hit the button Commit in the bottom-right corner. This will add the files to the Git repository and we can now see that all the files have returned to a black color in the project window. This means that all the files are now under version control. If we make a change to a file, the color will change appropriately. From now on, we can add single files and commit them either individually or as a group, just like the initial commit.
Now let's see how to view changes from different files versus our committed repository changes:
Add the following comment line to our
species.rbfile from app | models above the method that we created earlier:# Return a status string of a particular species
Save the file.
Right-click on the opened file and navigate to Git | Compare with Latest Repository Version. This will show us a window with both versions of the file shown next to each other with insertion and deletions from both versions to show exactly what is different between the two files, as you can see in the following screenshot:
The subversion and other version control systems that RubyMine integrates with are basically the same in operation. Explore the subversion system or any other VCS systems that you might be familiar with. Just remember to use one of them to maintain your legacy and not lose your best work.
There are many more controls that you can use with your VCS including comparing full directories, pushing your changes to a remote repository, creating patches, viewing and creating branches, and even integration with GitHub. Feel free to explore all these options on your own.