BT

Your opinion matters! Please fill in the InfoQ Survey!

Ruby On Rails State of Practice: Deployment and Management

| by Mirko Stocker  Followers on Jan 15, 2013 |

InfoQ's research widget has been deprecated. It should continue to work however, and we hope to relaunch it at some point in the future.

Rails developers can draw from a huge pool of libraries to build their applications. Dozens of options are available just for templating: do you use ERB, HAML, SASS, or do you prefer a JavaScript approach with Backbone.js or Knockout.js? The possibilities are endless, so we want to find out what our readers are using, or planning to use in the future.

In a first step (RFP), we asked you for suggestions. We received many answers, and now start with a first question about deployment & management. On the x-axis, you can show us what you’re using right now, or what you’ve moved away from and what you plan to adopt next. The y-axis indicates how valuable you think the specific technology or library is.

Here are the options:

  • Apache + Passenger: also known as mod_rails, fast and easy to install
  • Capistrano: running commands in parallel on multiple servers
  • Chef: infrastructure automation for your servers
  • Heroku: the cloud application platform
  • Lighttpd: the lightweight web server alternative
  • logstash: log and event management
  • Mongrel: the web server written in Ruby
  • Nagios: infrastructure monitoring
  • Nginx: high performance web server and proxy
  • Thin: fast and simple Ruby web server
  • Torquebox: Ruby application platform built on JBoss and JRuby
  • Trinidad: running your Rails or Rack applications on Tomcat
  • Unicorn: the Unix friendly HTTP server for fast clients

 

 

 

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Puppet & Chef by Michael Murray

You should include Puppet if you're going to include Chef

You are missing Ansible by Eric Brooke

You are missing Puma by Eric Brooke

github.com/puma/puma with 2860 stars, it is a big miss too.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

3 Discuss

Sponsored Content

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT