No commit activity in last 3 years
No release in over 3 years
Shoryuken integration for Capistrano
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
 Dependencies

Runtime

 Project Readme

capistrano-shoryuken

Shoryuken integration for Capistrano. Loosely based on capistrano-sidekiq

Installation

Add this line to your application's Gemfile:

gem 'capistrano-shoryuken', github: 'joekhoobyar/capistrano-shoryuken'

or:

gem 'capistrano-shoryuken', group: :development

And then execute:

$ bundle

Usage

    # Capfile

    require 'capistrano/shoryuken'

Configurable options, shown here with defaults (using Capistrano 3 syntax):

    # config/deploy.rb
    
    # Whether or not to hook into the default deployment recipe.
    set :shoryuken_default_hooks,  true
    
    set :shoryuken_pid,            -> { File.join(shared_path, 'tmp', 'pids', 'shoryuken.pid') }
    set :shoryuken_env,            -> { fetch(:rack_env, fetch(:rails_env, fetch(:stage))) }
    set :shoryuken_log,            -> { File.join(shared_path, 'log', 'shoryuken.log') }
    set :shoryuken_config,         -> { File.join(release_path, 'config', 'shoryuken.yml') }
    set :shoryuken_requires,       -> { [] }
    set :shoryuken_options,        -> { ['--rails'] }
    set :shoryuken_queues,         -> { [] }
    set :shoryuken_role,           :app

Changelog

  • 0.1.5: Bug fix when using Capistrano 2
  • 0.1.4: Minimum ruby 1.9.2
  • 0.1.3: Fix erroneous auto-loading from Bundler.require
  • 0.1.2: Support --require option.
  • 0.1.1: Default --rails option. Support Capistrano 3
  • 0.1.0: Support Capistrano 2

Contributors

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request