How do we start?

Hi Guys

Long time no see 🙂 sometimes I feel like I should tell that to myself as well.

So how do we start, we start by noting down what we need to do, and while we are at it, we note down what we didn’t write in the first place and also few more things which you should have thought of before. To do things is to improvise, learn and also to keep on adding more things to do, obviously a to-do list never ends, because to do something or to learn something, you need to do a lot of things 🙂

To understand that lets write a blog post 🙂 This is going to be quick. All you need is rails setup in your system.

Lets start with creating a blank app

rails new todoapp # this will create a blank slate for you to work on

rails g scaffold todo task:string complete:boolean parent_task_id:integer # this will create your model/views/controller/migration etc etc files which you will do the work for you

rake db:migrate # if this throws an error, you gotta do “rake db:setup first” this will create your database migration and the schema for todo tasks.

Now we need to build something like the below to sorta have a parent child relationship between the tasks. Why ? just read the 2nd para again from top.

Parent Task 1
—- Child Task 1
—- Child Task 2
Parent Task 2
Parent Task 3
—- Child Task 1
——– Child Task 2

In your new and shiny app/models/todo.rb add these two lines to create the parent child hierarchy.

has_many :child_tasks, :class_name => 'Todo', :foreign_key => "parent_task_id"
belongs_to :parent_task, :class_name => 'Todo', :foreign_key => "parent_task_id"

Now a bit of magic is needed to the views to allow us to easily select the Parent tasks for any child task.

Head over to your app/views/todos/_form.html.haml or *.erb file depending on the templating engine and change the f.parent_task_id to a collection_select

= f.label :parent_task_id
= collection_select :todo, :parent_task_id, Todo.all + [], :id, :task

This will allow us to choose a parent task, whenever we are creating a new task with – not a very bad hack? 😛

Finally in the show and index page, we need to display the parent task.

replace your todo.parent_task_id with
Todo.find_by_id(@todo.parent_task_id).task rescue "No Parent Task"

And the end result is tada!!!



A simple Tweet Retweeter

Hi Guys, So well on a lazy saturday afternoon, when you don’t have anything to do, you get this feeling to make something. So well what you do, you just make something simple, Burgers, fast food anything that you like. But well people like us who think, they are so called developers, have to feel the burden of creating something which which solve more a problem more important than the “What to have for lunch?” problem.

Anyways, so well, I have two twitter accounts, 1) @sudipto05 <– which I use and do follow me here and 2) @delhianimeclub which is my club’s twitter accout, which well, I never use, but well, its gets updated with the posts that are put on our facebook page. (If you are into anime, do like us on facebook). So the problem at hand, I had to manually retweet the tweets of @delhianimeclub from my other account, you know cross promotion, stuff like that. But this wasn’t really cool. right?

So what do Rails developers do?

This is what they do

rails new retweeter

Lets add a few gemfiles, of late I have had to work on HAML and Bootstrap so lets add those gems. Checkout my gemfile from link. We wont be really needing the twitter bootstrap gem for this iteration of the project, but we will be certainly using it for the making a statistics application for our twitter account. I don’t really like postgresql, but I wanted to host it on heroku,which only has support for pg. Oh yes, just forgot, two of the most important gems that we are going to use

1. Twitter gem – will let us post fetch and post tweets only with what 2 lines of code! I could have tried to use Twitter’s rest api too, but then, who is going to make lunch? huh?

2. Rufus Scheduler – I love this, its an awesome gem for scheduling your jobs, since we are going to check if new tweets are posted after regular intervals, we need some kind of cron job running behind our app, this is going to make it super easy.

After adding the gem files, just

bundle install

So here we go, now some actual coding starts, well yeah! twitter bootstrap gem doesnt like windows at all, so its better if you add the css and js files manually from link. You know right? they go into the assets folder 😛

Well, we are going to save the tweets in our database too, so lets generate a Tweet model with three fields.

rails g model Tweet tweet_id:string tweet_text:string tweeted_at:datetime

The advantage of specifying the attributes while generating a model is that they get automatically added to both the migration! duh! and also in the attr_accessible in the model file. Saves you 10 seconds of typing 😛

and afterwards to run the migration and setup our database

rake db:migrate

lets start with our Scheduler first. Create a new file in the config -> initializers directory, well you can name it anything, I just named it task_scheduler.rb and put in the snippet of code. A very simple explanation of the code within the file.

1) Requires the rufus scheduler gem, so we add the require line.

2) Create a new instance of the scheduler with

scheduler = Rufus::Scheduler.start_new

3) And lastly we simply call a class method within a block, which will call the method every 1 minute, now you can choose the duration of the interval according to your needs, 1 minute seems fair enough, its not like we post tweets faster. What? It requires aesthetics for tweeting? huh?

Okay so we are done with 33% percent of the work, Lets move onto our model file, Remember Tweet model that we created. Check out the file from link. Lets see what gibberish we have to put in the code now.

1. First we get the recent tweets of the user from whose account, we are going to retweet. latest_tweets = Twitter.user_timeline(“account_name”)

2. Then we run a simple loop through the recent tweets that we get from twitter and check if the tweet is present in the database, if not, the tweet will be retweeted and saved in the database.

3. Every tweet has its unique id which you can access using Tweet.attrs[:id] or Tweet.attrs[:id_str] which has the same value as :id_str, just use anyone you like, the twitter api says to not use the @attrs[:id] but thats applicable only for javascript code.

4. Oh yes! I have put this whole block of code within begin rescue end block, this twitter gem seems to throw in some weird exceptions sometimes, so just to log the errors, you can use the logger of your choice for this.

Okay, Guess we are done with 70% of the work 😀

So the next step is to create a new twitter application which is going to be used to post your tweets, don’t worry, we just need it for the config keys, nothing fancy.

1. Head over to link, to create a new twitter application. Oh yeah! sign in with the twitter account, using which you want to retweet the tweets from your other account.

2. Fill in the name and all description, just anything who cares 😛

3. After you are done with creating the app, go to settings and change the application type to “Read and Write” after this change save it and head back to the Details tab and create new access tokens. What? can’t you see, there is a button on the bottom to create new tokens.

These tokens will be used to authorize our rails app to post the tweets, oh yeah! the name you put for this app is going to show below every tweet 😛

You need to add these keys to your environments.rb file. Just check out the files here and add the lines for twitter config to the respective environment file in your app.

And we are done, just start the server and see the magic. Our initializer will run after 1 minute and fetch the latest tweets, save them in database and post them to our other twitter account. Thats it. What we have made a retweeter in less than what 30 lines of code, i guess, that is why I love ruby on rails. Oh! wait, you are going to tell me, that I made a rails app, just for this, when I could have done this using just a single ruby file, well yeah! the reason being, we are going to extend this web application in many many ways, so don’t forget to check the blog for updates. The code of this application is hosted on my github.

Choose the db adapter while creating a new application in rails

A lot of people are moving towards Ruby on Rails even at corporate level and giving up the standard Java, .Net way of developing websites for their customers. There are plenty of reasons for that, one of them being their argument that these languages are good at small level but are not scalable enough to solve the needs of corporate level customers. But now even developers who have been coding in java or other languages are increasing looking at solving their problems using frameworks such as Rails or Python/Django.  I believe the development curve of any language is steep only because of the time you want to devote to that language. I chose to devote some time to learn a few things in rails that makes life easy or atleast saves a bit of time. So lets see. lets make some rails stuff.

You would know that to create a new application all you need to do is type

rails new application_name

But this configures the application to use the sqlite3 database, If you want to use any other database, you would have to change it manually in the config->database.yml file. But there is a better way to do it, If you are sure, what database you are going to use, you can just specify it at the time to creating the application

rails new application_name -d mysql

The “-d” specifies the database name, you can use any of the databases from the list – mysql, oracle, postgresql, sqlite3, frontbase, ibm_db, sqlserver, jdbcmysql, jdbcsqlite3, jdbcpostgresql, jdbc.

No Ruby Version Manager on Windows.

Its true that there is no ruby version manager on windows, which makes life really difficult for a lot of ruby or rails developers I am sure, Well it did for me at least. A lot of applications developed in version 1.8.7 aren’t compatible with the new version. A lot of applications also fix themselves to use only specific versions of ruby, so there is not much we can do, unless you are a mega-geek and can change a lot of things and ofcourse have a lot of time. On linux we always have had RVM to solve this problem which lets us have different versions of ruby, different gemsets for each version of ruby, makes life really easy. But what for the windows developers? Thankfully a noble soul known as Gordon Thiesfeld made something amazing known as pik. which essentially works the same as Ruby version manager, with a few differences in installations but none in usage. Both of them are equally easy to use.

I am not going to write about how to install and use RVM, since there is enough help for that on the WWW. But Since I love windows users(I being one). We will have a walk-through with pik today. Before we start you can have a look at the github page of the project –

Installations –

It does mention that you need to install ruby 1.8.7 first to install pik, Now ruby 1.8.7 is an older version and I wonder, why would I need to install an older version to install a newer version, So first I went ahead and installed ruby 1.9.2-p290 from for installing pik. Seems it worked just fine. You can choose to install ruby 1.8.7 first and then install pik, its entirely upto you.

After installing Ruby make sure, you also have devkit installed, if you are a windows user you would know that ofcourse, dev kit is used to build the gems that are developed with native extensions, which means nothing, but those gems are made partially in ruby and partially using c. You can’t miss C anywhere can you. Anyways, I will give a quick guide about installing devkit, since you are going to need it anyways.

Head over to and download DevKit.
Installations steps
1. The file you downloaded is just an extractor, extract is to somewhere where you wont delete it by mistake.
2. After extraction, open up CMD and cd to the location where you extracted the files.
3. run

ruby dk.rb init

4. This will let you know the ruby installed in your system.
5. run

ruby dk.rb install

and you are done. Didn’t take too much time, did it?

Now we move on to pik installation steps
1. Fire up CMD and run

gem install pik

2. Now if you type

pik list

you will be able to see that it shows the base version of ruby that you installed. In my case, it shows

* 192: ruby 1.9.2p290 (2011-07-09) [i386-mingw32]

3. There are two ways of adding ruby versions to pik, either you install them manually and add to pik or you just install them through pik. We will see how to install them from pik, since we are going to use pik anyway, less bothersome to do it from pik, than downloading from the internet, installing each of them and then adding to pik.
4. Installing other version of ruby

pik install ruby 1.8.7

And here you go it will install the version of ruby and add that to pik by itself, Less of a hassle. right?
5. Check the versions of ruby installed in your system

pik list

6. Change the version of ruby that you want to use

pik use ruby [verions]

in my case

pik use ruby 1.8.7

7. Don’t forget to use the help if you get stuck.

pik help commands

Autotest Problems

Here is some problem that I encountered while ruby on rails development. You might know about TDD (Test Driven Development). Now since autotest can be used to speed up and automate the testing process somewhat and spork can be used to reduce the amount of time require d to run the tests. This becomes crucial that your tests are running smoothly.

The problem I encountered was that autotest continuously kept on testing all the cases.  Autotest is supposed to run only when there is any change made to the files that are referred in the test cases. So my autotest wasnt stopping even when I wasnt making any change. Autotest is a CPU intensive task, so it was necessary for me to find a workaround so it stops testing again and again till I actually make some changes..

The workaround to stop autotest from running if you dont make any change is  to add these lines to your .autotest file

autotest.add_exception %r{^\./db}
autotest.add_exception %r{^\./log}

My .autotest file looks like

require ‘autotest/growl’ # enable pop-up windows
require ‘autotest/restart’ # optional: forces autotest to pick the changes to this file
require ‘autotest/timestamp’ # optional: shows timestamps for test runs

# filter out VCS files and other garbage to reduce HDD usage

Autotest.add_hook :initialize do |autotest|
%w{.git .svn .hg .DS_Store ._* vendor tmp log doc}.each do |exception|
autotest.add_exception %r{^\./db}
autotest.add_exception %r{^\./log}

# do not clear console before running tests
Autotest::Growl::clear_terminal = false