Contents

# /etc/init/puma.conf - Puma config

# This example config should work with Ubuntu 12.04+.  It
# allows you to manage multiple Puma instances with
# Upstart, Ubuntu's native service management tool.
#
# See workers.conf for how to manage all Puma instances at once.
#
# Save this config as /etc/init/puma.conf then manage puma with:
#   sudo start puma app=PATH_TO_APP
#   sudo stop puma app=PATH_TO_APP
#   sudo status puma app=PATH_TO_APP
#
# or use the service command:
#   sudo service puma {start,stop,restart,status}
#

description "Puma Background Worker"

# no "start on", we don't want to automatically start
stop on (stopping puma-manager or runlevel [06])

# change apps to match your deployment user if you want to use this as a less privileged user (recommended!)
# setuid vagrant
# setgid vagrant

respawn
respawn limit 3 30

instance ${app}

script
# this script runs in /bin/sh by default
# respawn as bash so we can source in rbenv/rvm
# quoted heredoc to tell /bin/sh not to interpret
# variables
exec /bin/bash <<'EOT'
  # set HOME to the setuid user's home, there doesn't seem to be a better, portable way
  export HOME="$(eval echo ~$(id -un))"

  cd $app

  source /etc/profile.d/rbenv.sh

  source /etc/profile.d/custom_bundler_gemfile.sh

  logger -t puma "Starting server: $app"

  exec bundle exec puma -b unix://<%= socket_path %>
EOT
end script

Version data entries

2 entries across 1 versions & 1 rubygems

Version	Path
freighthop-0.0.1	local_modules/freighthop/templates/puma/upstart/puma.conf.erb
freighthop-0.0.1	modules/freighthop/templates/puma/upstart/puma.conf.erb