After a long time, I picked up to build a web application for a friend. I havent worked in web apps for about 6-8 months now, and was quite rusty.
Ruby on Rails was a natural choice. However, when I issued the "gem update" it turned out that rails is on 3.2.2 these days, which means there has been at least 4 releases since I last worked with rails.
I typically work in a way that learning happens while working only. Therefore, I just started building a new application and built a default scaffold (I know, its an old habit of testing installation using scaffold)... scaffold generated, which means that the backward compatibility is still alive. Server started.. and bang, launched chrome to see how localhost:3000 looks like...
it bombed... there was this "ExecJS::RuntimeError" staring at my face...
It turned out that Ubuntu is the culprit and needs nodejs to be installed as a JS runtime engine is required and by default Ubuntu doesnt provide one.
after "sudo apt-get install nodejs", its all smooth and shiney...
Will share further...
Ruby on Rails was a natural choice. However, when I issued the "gem update" it turned out that rails is on 3.2.2 these days, which means there has been at least 4 releases since I last worked with rails.
I typically work in a way that learning happens while working only. Therefore, I just started building a new application and built a default scaffold (I know, its an old habit of testing installation using scaffold)... scaffold generated, which means that the backward compatibility is still alive. Server started.. and bang, launched chrome to see how localhost:3000 looks like...
it bombed... there was this "ExecJS::RuntimeError" staring at my face...
It turned out that Ubuntu is the culprit and needs nodejs to be installed as a JS runtime engine is required and by default Ubuntu doesnt provide one.
after "sudo apt-get install nodejs", its all smooth and shiney...
Will share further...
No comments:
Post a Comment