RoR - Ruby on Rails
Get flash to fully experience Pearltrees
This Documentation Has Moved to rubyamqp.info amqp gem documentation guides are now hosted on rubyamqp.info . About this guide This guide is a quick tutorial that helps you to get started with v0.9.1 of the AMQP specification in general and the Ruby amqp gem in particular.
RabbitMQ and AMQP (Advanced Message Queuing Protocol) are gaining momentum in the market. One of the main reasons for that momentum is because, in enterprise development, the client is not always Java specific. With RabbitMQ, we can configure a scalable, fault-tolerant, open-source messaging solution for polyglot clients, click here to see a list of client language support. Follow the steps below to install and configure RabbitMQ v1.7.x on a MAC with OSX Lion.
This Documentation Has Moved to rubyamqp.info amqp gem documentation guides are now hosted on rubyamqp.info . About this guide This guide covers everything related to queues in the AMQP v0.9.1 specification, common usage scenarios and how to accomplish typical operations using the amqp gem. This work is licensed under a Creative Commons Attribution 3.0 Unported License (including images & stylesheets).
May 5th, 2010 UPDATE: The DataObjects drivers, which are used in DataMapper, are now updated to honor default_internal. Let’s keep this moving.
Actually this post is not so much about just building custom validators for Rails 3 but more like a in-depth introduction to how validations work in the old and new versions of rails. And in addition to that I’m going to implement Rails 3 compatibility for the validates_existence gem, which we maintain and use extensively in our projects. The “old” stuff First I’m going to give you a quick overview of the gems current functionality, plus basic explanation of how it’s implemented. The gem itself contains a single validation – validates_existence_of , which validates belongs_to relations by making a query to the database and checking if the record actually exists.
The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!)by Joel Spolsky Wednesday, October 08, 2003 Ever wonder about that mysterious Content-Type tag?
Today’s blog post is by a guest community contributor, Rizwan Reza . Rizwan is an active member of the Rails community, and as of late, has been working to clean up the overgrown Lighthouse queue. We’re happy to have him write for those seeking advice on deploying on a Platform as a Service . Stop!
June 28, 2010 A couple of weeks ago at a get-together of local developers, someone mentioned he hadn’t checked out Rails 3 yet because he didn’t want pre-release software mucking up his usual development environment. I don’t blame him—this is a reason I also put off checking out earlier releases of Rails 3.
July 05, 2010 I believe that Rails is an excellent way to get started on server-side web development. The framework provides a good structure that’s easy to understand, and provided you follow some fairly basic rules, you can have a functioning web application up and running pretty quickly. Add to that the gems and plugins that add near-instant functionality, and even newcomers can show off useful, good-looking web apps. Clicking through links and forms on an app you made yourself feels pretty good and should hopefully motivate you to want to do more.
The semantics of method calls in Ruby are simple: Call the named method; or If no method exists, call #method_missing() instead. Normally #send() obeys these rules as well. ActiveRecord association proxies mangle #send() ‘s semantics, however, violating the POLS and potentially breaking your code in the process. Let’s say we have some monsters: class Monster < ActiveRecord::Base has_many :friendships has_many :friends, :through => :friendships end class Friendship < ActiveRecord::Base belongs_to :monster belongs_to :friend, :class_name => "Monster" end cookie = Monster.create(:name => "Cookie Monster", :color => "blue") grover = Monster.create(:name => "Grover", :color => "blue") oscar = Monster.create(:name => "Oscar the Grouch", :color => "green") clancy = Monster.create(:name => "Clancy", :color => "green")