As part of InfoQ's ongoing Community Driven Research project, we want to learn more about the best practices in Ruby on Rails usage. In a first round, we are collecting suggestions for the voting options, from which we are then going to pick the most interesting ones and let the community rank them.
For example, we want to find out if developers go with Rails' templates or use a JavaScript framework such as Backbone.js or Knockout.js.
So what do you use to handle authentication? What's your favorite way to run your Rails applications in production? Which version or implementation of Ruby are you using? What do you use for testing? And monitoring?
Please let us know in the comments below or send an email to mirko.stocker@infoq.com.
Community comments
current stack
by brian walsh,
Current Practice
by Nosh Ghazanfar,
hospital-systems
by Nicola Rizhikov,
current stack
by brian walsh,
Your message is awaiting moderation. Thank you for participating in the discussion.
jruby. devise+ldap. trinidad thinking about torquebox.
Current Practice
by Nosh Ghazanfar,
Your message is awaiting moderation. Thank you for participating in the discussion.
Ruby 1.9.3,Rails 3,Devise for authentication,CarrierWave for file uploads, jquery and knockout.js. I would also prefer backbone.js. Reason for selecting a mvvm like javascript framework is to provide fluent and interactive experience to the users & better structure in client code, rather than ease of development purely on the server side.
hospital-systems
by Nicola Rizhikov,
Your message is awaiting moderation. Thank you for participating in the discussion.
postgresql, mongoid, twitter bootstrap, coffee, jquery, dojo, simple form, rspec, famili, capybara webkit, queue classic, capistrano and chef, spork, guard, unicorn