Restart puma when files change
Latest commit 11d0d9c Oct 12, 2015 @jc00ke Merge pull request #15 from glenngillen/optional-options
If config is provided it takes precedence.
Failed to load latest commit information.
lib/guard If config is provided it takes precedence. Sep 1, 2015
spec If config is provided it takes precedence. Sep 1, 2015
.travis.yml Run CI in container Sep 1, 2015
Gemfile Initial commit Mar 21, 2012
LICENSE Make quietness configurable Jun 14, 2013
Rakefile Default rake task runs specs Mar 21, 2012
guard-puma.gemspec Add guard-compat Sep 1, 2015


Build Status Dependency Status

Restart Puma when some files change


Add this line to your application's Gemfile:

gem 'guard-puma'

And then execute:

$ bundle

Or install it yourself as:

$ gem install guard-puma


guard init puma or add the following manually to your Guardfile

guard 'puma', :port => 4000 do


  • :port is the port number to run on (default 4000)
  • :environment is the environment to use (default development)
  • :start_on_start will start the server when starting Guard (default true)
  • :force_run kills any process that's holding open the listen port before attempting to (re)start Puma (default false).
  • :daemon runs the server as a daemon, without any output to the terminal that ran guard (default false).
  • :quiet runs the server in quiet mode, suppressing output (default true).
  • :debugger runs the server with the debugger enabled (default false). Required ruby-debug gem.
  • :timeout waits this number of seconds when restarting the Puma server before reporting there's a problem (default 20).
  • :config is the path to the Puma config file (optional)
  • :bind is URI to bind to (tcp:// and unix:// only) (optional)
  • :control_token is the token to use as authentication for the control server(optional)
  • :control_port is the port to use for the control server(optional)
  • :threads is the min:max number of threads to use. Defaults to 0:16 (optional)


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Leave the version alone!
  4. Add what you changed to
  5. Commit your changes (git commit -am 'Added some feature')
  6. Push to the branch (git push origin my-new-feature)
  7. Create new Pull Request