1. Post your requirements on twitter with hashtag #ruby #ror #rails
2. Go to Railsdevelopment.com - its a directory of rails companies. You can search for specific services with your budget ranges.
3. Working with Rails – Again a directory of rails developers and companies. You can browse through specific industry categories.
4. Local Ruby Meetups – The most passionate guys are always there in local meetups. For eg: we have delhi ruby meetups and you can find all local meetups in australia here
6. RubyJobs – Post a job on rubyjobs or rubyinside job board. There are some country specific ruby job boards.
7. RubyonRails wiki – There is a wiki of ruby on rails companies.
8. Open Source Contributions – Sites like http://agilewebdevelopment.com/ gives you a directory of rails plugins. Open Source contributions such as releasing a Rails plugin, or fixing bugs on projects , or Rails itself, demonstrates exposure to other Rails code bases and quality of a developer. Search for developer name in github.
9. Conferences – Conferences are good way to find quality rails developer or team.
10. Facebook – Few people post jobs on facebook.

Few tips :

• Don’t hire someone that doesn’t know Rails at all. Yes, we have seen some people doing it.
• Ask for references of previous clients if possible in your country.
• Look for someone who values the money you are paying them and will make your investment in them provide a valuable return.
• A personal Rails blog is a good indicator of  developer’s interests , experience and resume.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

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.

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

I gave an introductory presentation in VinSol. I am sharing it with you, this is not very explanatory as I focused on speech more. Please share your views.VinSol

| View | Upload your own

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:

1. rake db:test:purge
2. rake db:migrate
3. rake test

This default was not working with my last project As I was using RSpec for my project. I found that we can overwrite default way of building by creating a rake task named cruise in our project. Means by building CruiseControl will run your custom rake task only, so you have to take care of all other things i.e. migrate etc.

Hence I created following rake task in RAILS_ROOT/lib/tasks/custom_cc.rake

and it worked for my rails project using RSpec.