Our Rails deployments are run by passenger on the application servers, to automatically restart passenger workers after a deploy you should include the capistrano-passenger Gem in your Gemfile by...

...adding this line: gem 'capistrano-passenger', require: false And install it by calling bundle: $ bundle To actually be able to use the tasks this Gem provides you have to also...

opscomplete

.../var/www/$deployment/shared/log/ The logfiles written by your application should be stored here. /var/www/$deployment/log/passenger_all_apps.log Passenger is the application server used to run your rails application. If your application can not...

...are all gathered together in this one log file as the configuration option of passenger can be configured globally only. Due to that, this log is not available on shared...

...We are installing and configuring rbenv with the ruby-build plugin for your deploy user. Passenger-Ruby will get set to ${HOME}/.rbenv/shims/ruby There will be a cronjob which gets...

...have the same and correct ruby version on all your servers and that the passenger is using the correct ruby version. If you need to change the Ruby version please...

opscomplete

...these environment variables will be loaded if you login with your user and from passenger (rails) processes but are not read by your cronjobs or elixir application by default! You...

...describing an opinionated set up in this card. Install Capistrano Configure Capistrano Install capistrano-passenger Install capistrano-opscomplete Not using Git? Should you not be using Git, Capistrano also has...

Best results in other decks

github.com

...restarted several times. Through the project's history, these all were valid: touch tmp/restart.txt sudo passenger-config restart-app /path/to/app passenger-config restart-app /path/to/app You should not need to...

...ran with the current passenger instance (probably due to no requests to it) and the passenger-config command runs without superuser permissions. This won't stop or break your deploy...

With passenger-status --show=requests you can get a huge JSON showing current information about the running passenger processes. This can be useful if you want to find out what...

...running request or is stuck. You can search for the PID of the process in passenger-status --show=requests: # (this is just a snippet) "last_data_receive_time" : { "local" : "Wed...

Search in all decks