How to install ubiquo 0.9 – step by step tutorial

First of all, you need to have an account in github (https://github.com).

Later, you must add your SSH key to GitHub. You can follow the instructions of how to generate the SSH key and how to add it to GitHub here:

https://help.github.com/articles/connecting-to-github-with-ssh/

Then, once you have the GitHub account configured, you have to go to Ubiquo’s GitHub ( https://github.com/gnuine/ubiquo ) and fork it. In this way, you will have your own repo of Ubiquo.

The next step will be to clone the own repo of Ubiquo
(e.g. git clone git://github.com/davidruizrodri/ubiquo.git ubiquogems09)

Later, you can create a remote branch to work in it. To do this, follow this steps:

$ cd ubiquogems09/
$ git checkout -b work
$ git push origin work

It’s possible that the last command has thrown an error like this:

fatal: protocol error: expected sha/ref, got ‘ERR
You can’t push to git://github.com/davidruizrodri/ubiquo.git
Use git@github.com:davidruizrodri/ubiquo.git’

This is because the url of remote “origin” in .git/config file is bad configured. You must change it to “git@github.com:davidruizrodri/ubiquo.git”.

The next step will be to install ruby 1.9.3 in rvm, because it’s needed in Ubiquo 0.9 which uses Rails 3.2.6. To install it, you have to run “rvm install 1.9.3” in the console.

Later, you must install “jeweler” gem. (Optionally, you can create a gemset for a better organization of your gems).

Then, you go to “installer/” folder and run “rake build”. This rake generates the ubiquo 0.9 gem. Once it’s generated, you have to install it:

$ gem install pkg/ubiquo-0.9.0.b9.gem

At this point, we can create an ubiquo project using the gems of your own repo of Ubiquo:

$ ubiquo --edge --devel --rvm --gem-path ABSOLUTE_PATH_TO_OWN_REPO PROJECT_NAME

Finally, if you want to keep your own repo of Ubiquo updated with the changes of the original repo, you must follow the instructions of this page https://help.github.com/articles/fork-a-repo/ (“Step 3: Configure remotes” and “Pull in Upstream changes” sections.