No commit activity in last 3 years
No release in over 3 years
Cat release file if it changes
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Runtime

 Project Readme

Capistrano::Release

Really help not to forget do a one time stuff after/before deploy.

You put a needing text in file doc/do_on_release.txt (or you particular sets in variable release_file), like: «Reindex index» or «Run rake stat:count»

On deploy cats this file if context is change

Options.

set :release_file, fetch(:release_file, 'doc/do_on_release.txt') # What file compare
set :release_ask, fetch(:release_ask, true) # Pause deploy after cat changes release

Add this line to your application's Gemfile:

gem 'capistrano',  '~> 3.4'
gem 'capistrano-release', '~> 0.3'

Usage

Require

# Capfile
require 'capistrano/release'

Please note that any require should be placed in Capfile, not config/deploy.rb.

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