Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/petems/boxen-module-maker

Make new boxen modules quickly and easy from the command-line.
https://github.com/petems/boxen-module-maker

Last synced: about 1 month ago
JSON representation

Make new boxen modules quickly and easy from the command-line.

Host: GitHub
URL: https://github.com/petems/boxen-module-maker
Owner: petems
License: mit
Created: 2013-03-30T02:02:02.000Z (over 11 years ago)
Default Branch: master
Last Pushed: 2013-04-18T12:58:40.000Z (over 11 years ago)
Last Synced: 2024-10-03T09:57:47.994Z (about 2 months ago)
Language: Ruby
Homepage:
Size: 176 KB
Stars: 2
Watchers: 3
Forks: 0
Open Issues: 0
Metadata Files:
- Readme: README.md
- License: LICENSE.txt

Awesome Lists containing this project

README

# boxen-module-maker

A gem for creating boxen modules easier! :)

## Basic Use
```bash
$ gem install boxen-module-maker
$ boxen-module-maker new_app
boxen-module-maker: [CREATE FOLDER] Making 'puppet-new_app'
create puppet-new_app
$ cd puppet-new_app
$ ls
ls
CONTRIBUTING.md Gemfile Gemfile.lock LICENSE README.md manifests script spec
```

Currently, it will create a folder with your given name with the word `puppet` in front of it,
clone [puppet-template](https://github.com/boxen/puppet-template) folder,
and edit the manifest file and spec file so the specs will pass immediately.

## TO-DOS

* Clean up the structure (I took it from a template and kinda bodged it together)
* Make it automatically run `script/cibuild` on the folder
* Fix up the specs (ie. Add some...)

## Contributing to boxen-module-maker

* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.
* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.
* Fork the project.
* Start a feature/bugfix branch with a sensible name
* Commit and push until you are happy with your contribution.
* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
* Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.