我浏览了整个互联网，但无法做到这一点。需要在VDS（Ubuntu 14.04）启动时启动Sidekiq。我找到并使用了以下内容：
# /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 manage sidekiq with:
# sudo start sidekiq index=0
# sudo stop sidekiq index=0
# sudo status sidekiq index=0
#
# Hack Upstart's reload command to 'quiet' Sidekiq:
#
# sudo reload sidekiq index=0
#
# or use the service command:
# sudo service sidekiq {start,stop,restart,status}
#
description "Sidekiq Background Worker"
start on startup
#start on runlevel [2345]
stop on runlevel [06]
#start on startup
# change to match your deployment user
setuid me
setgid me
env HOME=/home/me
respawn
respawn limit 3 30
# TERM is sent by sidekiqctl when stopping sidekiq. Without declaring these as
# normal exit codes, it just respawns.
normal exit 0 TERM
# Older versions of Upstart might not support the reload command and need
# this commented out.
reload signal USR1
instance $index
script
# this script runs in /bin/sh by default
# respawn as bash so we can source in rbenv
exec /bin/bash <<'EOT'
# Pick your poison :) Or none if you're using a system wide installed Ruby.
# rbenv
# source /home/apps/.bash_profile
# OR
# source /home/apps/.profile
# OR system:
# source /etc/profile.d/rbenv.sh
#
rvm
source /usr/local/rvm/scripts/rvm
# Logs out to /var/log/upstart/sidekiq.log by default
cd /var/www/vk_c_watcher/code
exec bundle exec sidekiq -i ${index} -e production
EOT
end script
添加之后，我可以使用 start sidekiq app="/var/www/vk_c_watcher/code" index=0 启动Sidekiq。但是重启后，进程列表中没有Sidekiq。