30 Apr 2008

RubyOnRails Plugin: Auto Tags

RubyonRails, auto_tags, networking, open_source, plugin posted by SUR

Announcing the release of this tiny useful plugin AutoTags.
A couple of weeks ago I travelled to Mumbai in train which was a long 17hrs journey… and I utilized that by coding down the idea while travelling. So here it comes…

AutoTags, an open source project, is a plugin for RubyOnRails applications to automatically generate the relevant tags for the provided content. Its quite simple to use and provide easy integration with ActiveRecord. The plugin is very useful for social applications, community websites and all those networking applications where there is a scope of user generate content to be tagged. No more heck for the admin to sit and add the tags to the content or waiting for the users to add the tags to their content.

For installation and usage read here.

If you liked the plugin then please recommend me on workingwithrails.

23 Apr 2008

Git Error: trailing whitespace, indent SP followed by a TAB, unresolved merge conflict

Git, RubyonRails, SCM, Tools, VCS, pre-commit, rails posted by Akhil Bansal

I have been using Git from last few days, and faced following errors while committing:

1) Trailing whitespace
2) Indent SP followed by a TAB
3) Unresolved merge conflict

The first error “Trailing whitespace” is because of carriage-return/line-feed(windows style line feed/end). To resolve this problem comment following lines(58-60) in .git/hooks/pre-commit file:

The second one “Indent SP followed by a TAB” is because of leading spaces/tabs. To resolve this problem comment following lines(61-63) in .git/hooks/pre-commit file:

The third one “Unresolved merge conflict” is because of seven or more successive occurrence of = or < or > characters. Major chances of having seven = character in README or doc files. To resolve this problem replace following line(64) in .git/hooks/pre-commit file:

by

These tricks worked for me, I hope it could help you.

23 Apr 2008

Rails Plugin Annotate Models For Spec And Spec Fixtures

Git, RubyonRails, Tools, VCS, annotate_models, patch, rails, rails plugins, ruby, subversion, svn posted by Akhil Bansal

I have been using “Annotate Models” rails plugin written by Dave Thomas since I found it around one and half year ago. It really helps while writing fixtures. But if you use RSpec you might miss schema info at the top of your rspec fixture file as I do. So, today I modify the plugin file so that it prepends schema info to spec file and fixture file. Below are the links of patch file:

svn patch to add schema info to spec file and spec fixture file
git patch to add schema info to spec file and spec fixture file

23 Jan 2008

Migration: Adding/Removing columns are now much easier

RubyonRails, Technology, migration, rails, ruby, web development posted by Akhil Bansal

You may have noticed by now, that in Rails 2.0 changeset 7422, you can specify columns you want to add/remove in your migration by passing attribute:type pairs to the migration generator.

For example, lets assume that we need to add a column ‘role’ in users table(User model). In this case generate a migration like:

Output:

Here AddRoleToUser plays the main role. ‘Add’ specifies the we want to add column(s) and ‘User’ separated by ‘To’ specifies the table.

Similarly, if we need to remove a column ‘role’ :

Output:

Here RemoveRoleFromUser plays the main role. ‘Remove’ specifies the we want to remove column(s) and ‘User’ separated by ‘From’ specifies the table.

Isn’t it cool?

14 Jan 2008

Ruby Script for SVN commit notification with log message, list of updated files and readable colored SVN Diff

RubyonRails, Technology, Tools, notification, rails, ruby, subversion, web development posted by Akhil Bansal

Some days ago I wrote a post about “SVN commit notification” which uses a perl script for sending commit notification with svn diff by mail. In this mail you can find svn diff from the last committed revision. I used to love this mail, soon I realized that it is a bit ugly and difficult to read. Also there were some important information missing. Like the name of user committing the code, the log message etc…

And then I started writing my own ruby script for same purpose but with some addition and modification. Commit notification script is that script, you can download and configure it with your SVN post commit hook as follows.

Add following line at the bottom of your post-commit file:

* Please remember to change the path of you commit-email ruby script.

Now open commit-email ruby file and modify the following section according to your requirement:

You are done with that, now onwards whenever someone commits the code, you’ll get the commit notification mail like:

Commit Email Preview

Next Page »« Previous Page