# Adjust setting below to your local environment and than start puma like this:
# and manage it like this:
# For more information see http://www.rubydoc.info/gems/puma/
environment 'production'
# For non-thread-capable ruby impl. like MRI modifying this is usually just
# a waste of resources. However, for Rubinius or JRuby it probably makes a
# difference - in this case don't forget to adjust the workers accordingly.
# Perhaps starting with 75% of available strands is ok - monitor and adjust.
workers 24
# For convinience make it the same as for 'rails server', i.e. listen on all
# available interfaces on port 3000
bind 'tcp://0.0.0.0:3000'
# We don't like noise
# IMPORTANT wrt. MRI ruby - saves rsources!
# Invoke rolling restart of workers to keep memory down
before_fork do
require 'puma_worker_killer'
end
# let's make sure, that ppl with the same GID as the running puma process
# are really able to control puma (the group needs write access). See option
# --control and --control-url above.
if @options[:control_url]
end
end
end