Project

put_rake

0.0
No release in over a year
Put a template of Rakefiles on the local dir.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

>= 0

Runtime

 Project Readme

https://badge.fury.io/rb/put_rake.svg

PutRake

Put a template of Rakefile for the specific tasks on the local directory

Installation

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

$ bundle add put_rake

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

$ gem install put_rake

Usage

put_rake commands:
  put_rake add PATH        # add Rakefile template PATH
  put_rake for [EXT]       # put Rakefile for [EXT]
  put_rake help [COMMAND]  # Describe available commands or one specific command
  put_rake list            # list available Rakefiles
  put_rake path            # show Rakefile template path
  put_rake version         # show version

Put a Rakefile [for] a specific tasks. The default templates are located on the install directory of libs,

> put_rake path
* Rakefile template paths
  /Users/hoge/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/put_rake-0.1.3/lib/templates

and the additionals can be located any path which is specified by the following command:

put_rake add /Users/hoge/bin/Rakefiles

Happy Ruby.

Development

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/daddygongon/put_rake. 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 PutRake project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.