0.0
The project is in a healthy, maintained state
Capistrano plugin to manage cron jobs created from the whenever gem
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Runtime

~> 0.10
 Project Readme

Capistrano::Cron

The gem is based on whenever code. The difference is that crontab file is generated and uploaded to the server during deployment. No bin/whenever is needed on the server. It handles well asdf too.

Installation

TODO: Replace capistrano-cron with your gem name right after releasing it to RubyGems.org. Please do not do it earlier due to security reasons. Alternatively, replace this section with instructions to install your gem from git if you don't plan to release to RubyGems.org.

Install the gem and add to the application's Gemfile by executing:

$ bundle add capistrano-cron

If bundler is not being used to manage dependencies, install the gem by executing:

$ gem install capistrano-cron

In your Capfile, require the library:

require 'capistrano/cron'
install_plugin Capistrano::Cron

Usage

cap <stage> cron:update
cap <stage> cron:clear

Development

After checking out the repo, run bin/setup to install dependencies. Then, run rake test to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and the created tag, and push the .gem file to rubygems.org.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/codeur/capistrano-cron. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.

License

The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the Capistrano::Cron project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.