You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Feature request #1621: Switch to unicorn executable, drop unicorn_rails

Kind feature request
Product wincent.dev
When Created , updated
Status closed
Reporter Greg Hurrell
Tags no tags

Description

It [unicorn_rails] is designed to help Rails 1.x and 2.y users transition to Rack, but it is NOT needed for Rails 3 applications. Rails 3 users are encouraged to use unicorn(1) instead of unicorn_rails(1). Users of Rails 1.x/2.y may also use unicorn(1) instead of unicorn_rails(1).

See:

Comments

  1. Greg Hurrell

    From http://www.engineyard.com/blog/2010/everything-you-need-to-know-about-unicorn/:

    What is the unicorn executable? What is the unicorn_rails executable?

    The unicorn executable is a Rack-only tool modeled after Rack's "rackup" and is recommended for Rack applications. unicorn_rails was made to be an easier transition for users of pre-Rack versions of Rails. The manpage encourages Rails 3 users to use plain unicorn instead.

    What's the difference?

    From the unicorn_rails manpage, some conventions of unicorn_rails are modeled after script/server found in Rails. It creates directories under "tmp" like script/server and the -E/–environment switch sets RAILS_ENV instead of RACK_ENV.

  2. Greg Hurrell

    To ease the Rails 3 upgrade process, would be nice if I could switch to unicorn from unicorn_rails in my existing Rails 2.3.5 application. I wonder whether copying vendor/rails/railties/dispatches/config.ru into the app root will be enough. It contains: 

    # Rack Dispatcher

# Require your environment file to bootstrap Rails
require File.dirname(__FILE__) + '/config/environment'

# Dispatch the request
run ActionController::Dispatcher.new
  3. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu