This problem happens when I try to use rspec testing for Radiant. Radiant keep giving me error when I try to run spec for one of the extensions. The error is missing rspec gem. But my rspec gem is there. So i just run gem install rspec again. It helps me installed the latest version of rspec and all its related gems. I run spec command again, it gives me error again. In the end, I realize that Radiant is using older version of Rspec 1.3. So I have to install that version although it gives me error saying missing Rspec. After so many times of installing I messed up all the gems. So I wanna reinstall my ruby and all gems, here is how I did it. Before that, you probably wanna make a copy of what gems you have installed

gem list > ~/Desktop/installed_gems.txt

sudo rm -r /System/Library/Frameworks/Ruby.framework/
sudo rm -r /Library/Ruby
sudo rm /usr/bin/ruby
sudo rm /usr/bin/gem

Now you have removed all ruby and ruby gems. You should use Ruby Version Managers to install ruby on your mac. It will help you manage ruby properly. You can follow previous article on how to install rvm and ruby on mac.
Read the rest of this entry »

Mac OS is awesome, however there are a lot of softwares that only available in Windows. When this happens you have to switch back to windows computer. Or else, you might have used bootcamp to installed Windows OS in your computer. However, using dual OS it means that you have to restart your computers to switch to the other OS. This is very painful. I have this experience using Ubuntu. After a few months, I gave up and use Windows only. However, now with Parallels Desktop, everything becomes so awesome.

This is my desktop. You can see that I am running TVU player’s windows version and ShareInvestor Station side by side in Mac! All the windows application becomes just like a normal application in your mac. So you don’t have to restart your computer to access the windows applications. This is just awesome. However, the Parallels Desktop will allocate a certain amount of CPU and memory resources for Windows.

If you want to connect to a svn repository server in mac, here is what you should set up ssh configuration files under ~/.ssh/config

.ssh is a hidden folder, under that you have a config files
open the config file using the following command or you could use any editor you like to open the file

open ~/.ssh/config

Put the following configuration in the file:

Host your_svn_host_name
  User user_name_to_the_host
  IdentityFile ~/.ssh/id_rsa
  IdentitiesOnly yes

Here is the explanation to the settings. You can find it when you do

man ssh_config

IdentityFile
It is a private file that the ssh will use to connect to your svn repository servers. If you didn’t specify this. It will prompt you to enter the password to connect to the server instead. Here is the explanation after running ‘man ssh_config’: Specifies a file from which the user’s RSA or DSA authentication identity is read. The default is ~/.ssh/identity for protocol version 1, and ~/.ssh/id_rsa and ~/.ssh/id_dsa for protocol version 2. Additionally, any identities represented by the authentication agent will be used for authentication. The file name may use the tilde syntax to refer to a user’s home directory. It is possible to have multiple identity files specified in configuration files; all these identities will be tried in sequence. If you want to specify a different identity files, just change the name of the file under IdentityFile.

Do note that the id_rsa file must have the proper permission settings, otherwise when you run the following command to connect to your svn server:

ssh you_host_name

You will see the following error:

Permissions 0755 for ‘~/.ssh/id_rsa’ are too open.
It is recommended that your private key files are NOT accessible by others.
This private key will be ignored.

When you see this, you should set the permission back to default, so it can only have read access by you.

chmod 600 ~/.ssh/id_rsa

Now you should be able to connect to your svn repository.