Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When deploying my Rails app via Capistrano, the very last thing it tries to execute is this:
sudo -p 'sudo password: ' -u app /home/user/public_html/example.com/current/script/process/reaper
Then it throws this error:
failed: "sh -c \"sudo -p 'sudo password: ' -u app /home/user/public_html/example.com/current/script/process/reaper\"" on 123.456.789.012
The app still deploys and starts fine…but what does process/reaper do and what can I do to get rid of the error?
Before the Mongrel/Passenger epoch and before being build upon Rack, the only way to run a Rails application was using CGI or FGCI.
The script/reaper file was used to start/stop a Rails process.
By default, Capistrano tries to start a new Rails process running the reaper script.
You should customize the default behaviour.
Assuming you are running your Rails app using Passenger (mod_rails), install the following Capistrano + Passenger (mod_rails) recipe and Capistrano will gracefully restart your Passenger instance on deploy.