2013-02-19 00:19:14 -05:00
|
|
|
# /etc/init/sidekiq.conf - Sidekiq config
|
|
|
|
|
|
|
|
# This example config should work with Ubuntu 12.04+. It
|
|
|
|
# allows you to manage multiple Sidekiq instances with
|
|
|
|
# Upstart, Ubuntu's native service management tool.
|
|
|
|
#
|
|
|
|
# See workers.conf for how to manage all Sidekiq instances at once.
|
|
|
|
#
|
|
|
|
# Save this config as /etc/init/sidekiq.conf then mange sidekiq with:
|
|
|
|
# sudo start sidekiq index=0
|
|
|
|
# sudo stop sidekiq index=0
|
|
|
|
# sudo status sidekiq index=0
|
|
|
|
#
|
|
|
|
# or use the service command:
|
|
|
|
# sudo service sidekiq {start,stop,restart,status}
|
|
|
|
#
|
|
|
|
|
|
|
|
description "Sidekiq Background Worker"
|
|
|
|
|
|
|
|
# no "start on", we don't want to automatically start
|
|
|
|
stop on (stopping workers or runlevel [06])
|
|
|
|
|
|
|
|
# change to match your deployment user
|
|
|
|
setuid deploy
|
|
|
|
setgid deploy
|
|
|
|
|
|
|
|
respawn
|
|
|
|
respawn limit 3 30
|
|
|
|
|
2014-07-28 16:50:47 -04:00
|
|
|
# TERM is sent by sidekiqctl when stopping sidekiq. Without declaring these as normal exit codes, it just respawns.
|
|
|
|
normal exit 0 TERM
|
2013-10-03 14:18:05 -04:00
|
|
|
|
2013-02-19 00:19:14 -05:00
|
|
|
instance $index
|
|
|
|
|
|
|
|
script
|
|
|
|
# this script runs in /bin/sh by default
|
|
|
|
# respawn as bash so we can source in rbenv
|
|
|
|
exec /bin/bash <<EOT
|
|
|
|
# use syslog for logging
|
|
|
|
exec &> /dev/kmsg
|
|
|
|
|
|
|
|
# pull in system rbenv
|
|
|
|
export HOME=/home/deploy
|
|
|
|
source /etc/profile.d/rbenv.sh
|
|
|
|
|
|
|
|
cd /opt/theclymb/current
|
2014-04-28 23:28:00 -04:00
|
|
|
exec bin/sidekiq -i ${index} -e production
|
2013-02-19 00:19:14 -05:00
|
|
|
EOT
|
|
|
|
end script
|