Best practice for starting Juggernaut in production

[darth]

Hi,

how do you recommend to start juggernaut? I'm currently not using
Capistrano for deployment (yes, shame on me).

I've came up with only one solution, which is running juggernaut via
SSH with "nohup" command, but that doesn't seem like a very good
solution to me.

[bogdan]

-d option makes run as a daemon.

[patfrat]

I have set up my own service in the /etc/init.d/ path like this :

#!/bin/sh -e
APP_PATH=/path/to/my/rails_app
JUGGERNAUT_CONFIG="$APP_PATH/config/juggernaut.yml"
JUGGERNAUT_PID="$APP_PATH/tmp/pids/juggernaut.pid"
JUGGERNAUT_LOG="$APP_PATH/log/juggernaut.log"
RAILS_ENV=production
case $1 in
start)
echo "Starting Juggernaut ..."
juggernaut -d -c $JUGGERNAUT_CONFIG --pid $JUGGERNAUT_PID --log
$JUGGERNAUT_LOG
;;
stop)
echo "Stopping Juggernaut ..."
juggernaut -k * -c $JUGGERNAUT_CONFIG --pid $JUGGERNAUT_PID --log
$JUGGERNAUT_LOG
;;
restart)
echo "Juggernaut restart ..."
echo "Stopping Juggernaut ..."
juggernaut -k * -c $JUGGERNAUT_CONFIG --pid $JUGGERNAUT_PID --log
$JUGGERNAUT_LOG
echo "Starting Juggernaut ..."
juggernaut -d -c $JUGGERNAUT_CONFIG --pid $JUGGERNAUT_PID --log
$JUGGERNAUT_LOG
;;
esac