455c8740bd
The state saving works like saving the pidfile, but it contains much more rich information about the running server. Additionally, added the --status option to start the status server so that the server can be controlled over HTTP. The state file contains the information about where the status server is located. |
||
---|---|---|
bin | ||
ext/puma_http11 | ||
lib | ||
test | ||
tools | ||
.gitignore | ||
.travis.yml | ||
COPYING | ||
Gemfile | ||
History.txt | ||
LICENSE | ||
Manifest.txt | ||
puma.gemspec | ||
Rakefile | ||
README.md | ||
TODO |
Puma: A Ruby Web Server Built For Concurrency
Description
Puma is a small library that provides a very fast and concurrent HTTP 1.1 server for Ruby web applications. It is designed for running rack apps only.
What makes Puma so fast is the careful use of an Ragel extension to provide fast, accurate HTTP 1.1 protocol parsing. This makes the server scream without too many portability issues.
License
Puma is copyright 2011 Evan Phoenix and contributors. It is licensed under the BSD license. See the include LICENSE file for details.
Quick Start
The easiest way to get started with Puma is to install it via RubyGems and then run a Ruby on Rails application. You can do this easily:
$ gem install puma
Now you should have the puma command available in your PATH, so just do the following:
$ puma app.ru
Install
$ gem install puma
Advanced Setup
Sinatra
You can run your Sinatra application with Puma from the command line like this:
$ ruby app.rb -s Puma
Or you can configure your application to always use Puma:
require 'sinatra'
configure { set :server, :puma }
If you use Bundler, make sure you add Puma to your Gemfile (see below).
Rails
First, make sure Puma is in your Gemfile:
gem 'puma'
Then start your server with the rails
command:
$ rails s puma
Rackup
You can pass it as an option to rackup
:
$ rackup -s puma
Alternatively, you can modify your config.ru
to choose Puma by default, by adding the following as the first line:
#\ -s puma