Rails 2 support about puma

[rkh]

Rails 2.3.x should be supported, we might have to add docs there.

I was able to get Puma working with Rails 2.3.14 by doing the following:

Freeze Rails

$ rake rails:freeze:gems

Modify action_controller in file: vendor/rails/actionpack/lib/action_controller.rb by changing:

gem 'rack', '~> 1.1.0'

To:

gem 'rack', '~> 1.4.0'

Create config.ru file in project root:

http://guides.rubyonrails.org/v2.3.11/rails_on_rack.html

Then instead of using script/server, use:

$ rackup -s puma

Disclaimer: There may be issues running Rails 2.3 with Rack 1.4???

These links may be of use:
http://wiki.dreamhost.com/Ruby_on_Rails#Rails_2.3.5_-_Rack_1.0_already_activated_.28fix.29
http://stackoverflow.com/questions/1814856/bypassing-rack-version-error-using-rails-2-3-5

[hron84]

It needs more support than dropping a config.ru file into RAILS_ROOT?

[evanphx]

Someone needs to release a rails 2 rack adapter.

[Hareramrai]

Hi there,
I am trying to update the our application server to use puma from unicorn. I am using Rails 2.3.18 & Ruby 1.9.3. I have followed all steps given in https://devcenter.heroku.com/articles/deploying-rails-applications-with-the-puma-web-server . But I got the bellow error in our server log.

foreman start -p 3000
15:10:55 web.1            | started with pid 5395
15:10:55 worker.1         | started with pid 5397
15:10:55 monitor_daemon.1 | started with pid 5400
15:10:58 web.1            | [5399] Puma starting in cluster mode...
15:10:58 web.1            | [5399] * Version 2.11.3 (ruby 1.9.3-p484), codename: Intrepid Squirrel
15:10:58 web.1            | [5399] * Min threads: 1, max threads: 1
15:10:58 web.1            | [5399] * Environment: development
15:10:58 web.1            | [5399] * Process workers: 3
15:10:58 web.1            | [5399] * Preloading application
15:10:58 web.1            | [5399] ERROR: No application configured, nothing to run
15:10:58 web.1            | exited with code 1
15:10:58 system           | sending SIGTERM to all processes
15:10:58 worker.1         | terminated by SIGTERM
15:10:58 monitor_daemon.1 | terminated by SIGTERM

Please help me on this.
Thanks,
Hare

[hron84]

@Hareramrai you just missed a very important point of the documentation.
The documentation says the following:

This should point at your applications config.ru, which is automatically generated by Rails when you create a new project.

The second part of the sentence is simply not true in your case, since Rails 2.3.x does not generate config.ru automatically, you have to write one for yourself.

I recommend you to read this thread on StackOverflow about the topic, both the opening post and the linked solution too.