bash3boilerplate/README.md

91 lines
4.0 KiB
Markdown
Raw Permalink Normal View History

2014-01-12 12:03:32 +01:00
# bash3boilerplate
<!-- badges/ -->
[![Build Status](https://secure.travis-ci.org/kvz/bash3boilerplate.png?branch=master)](http://travis-ci.org/kvz/bash3boilerplate "Check this project's build status on TravisCI")
[![Gittip donate button](http://img.shields.io/gittip/kvz.png)](https://www.gittip.com/kvz/ "Sponsor the development of bash3boilerplate via Gittip")
[![Flattr donate button](http://img.shields.io/flattr/donate.png?color=yellow)](https://flattr.com/submit/auto?user_id=kvz&url=https://github.com/kvz/bash3boilerplate&title=bash3boilerplate&language=&tags=github&category=software "Sponsor the development of bash3boilerplate via Flattr")
[![PayPayl donate button](http://img.shields.io/paypal/donate.png?color=yellow)](https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=kevin%40vanzonneveld%2enet&lc=NL&item_name=Open%20source%20donation%20to%20Kevin%20van%20Zonneveld&currency_code=USD&bn=PP-DonationsBF%3abtn_donate_SM%2egif%3aNonHosted "Sponsor the development of bash3boilerplate via Paypal")
[![BitCoin donate button](http://img.shields.io/bitcoin/donate.png?color=yellow)](https://coinbase.com/checkouts/19BtCjLCboRgTAXiaEvnvkdoRyjd843Dg2 "Sponsor the development of bash3boilerplate via BitCoin")
<!-- /badges -->
2013-02-25 23:54:34 +01:00
When hacking up BASH scripts, I often find there are some
2013-02-25 23:39:31 +01:00
higherlevel things like logging, configuration, commandline argument
2013-02-25 23:54:34 +01:00
parsing that:
2013-02-25 23:39:31 +01:00
- I need everytime
2013-02-25 23:54:34 +01:00
- Take quite some effort to get right
- Keep you from your actual work
2013-02-25 23:39:31 +01:00
Here's an attempt to bundle those things in a generalized way so that
they are reusable as-is in most of my (and hopefully your, if not ping
me) programs.
2013-02-26 00:30:30 +01:00
An up to date [intro is found on my blog](http://kvz.io/blog/2013/02/26/introducing-bash3boilerplate/).
2013-02-25 23:39:31 +01:00
2014-11-04 15:23:05 +01:00
## Installation
There are 3 ways you can install (parts of) b3bp:
1. Just get the main template: `wget https://raw.githubusercontent.com/kvz/bash3boilerplate/master/main.sh`
2. Clone the entire project: `git clone git@github.com:kvz/bash3boilerplate.git`
3. As of `v1.0.3`, b3bp can be installed as a `package.json` dependency via: `npm install --save bash3boilerplate`
Although `3` introduces a node.js dependency, this does allow for easy version pinning & distrubtions in environments that already have this prerequisite. But nothing prevents you from just using `curl` and keep your project or build system low on external dependencies.
2013-02-26 00:30:30 +01:00
## Versioning
2013-02-25 23:39:31 +01:00
2013-03-27 16:05:58 +01:00
This project implements the Semantic Versioning guidelines.
2013-02-25 23:39:31 +01:00
2013-02-26 00:30:30 +01:00
Releases will be numbered with the following format:
2013-02-25 23:39:31 +01:00
2013-02-26 00:30:30 +01:00
`<major>.<minor>.<patch>`
2013-02-25 23:39:31 +01:00
2013-02-26 00:30:30 +01:00
And constructed with the following guidelines:
2013-02-25 23:39:31 +01:00
2013-02-26 00:30:30 +01:00
* Breaking backward compatibility bumps the major (and resets the minor and patch)
* New additions without breaking backward compatibility bumps the minor (and resets the patch)
* Bug fixes and misc changes bumps the patch
2013-02-25 23:39:31 +01:00
2013-03-27 17:54:31 +01:00
For more information on SemVer, please visit [http://semver.org](http://semver.org).
2013-03-27 16:08:31 +01:00
2014-11-04 15:23:05 +01:00
## Best practices
As of `v1.0.3`, b3bp adds some nice re-usable libraries in `./src`. Later on we'll be using snippets inside this directory to build custom packages. In order to make the snippets in `./src` more useful, we recommend these guidelines.
### Library exports
It's nice to have a bash package that can be used in the terminal and also be invoked as a command line function. To achieve this the exporting of your functionality *should* follow this pattern:
```bash
if [ "${BASH_SOURCE[0]}" != ${0} ]; then
export -f my_script
else
my_script "${@}"
exit $?
fi
```
This allows a user to `source` your script or invoke as a script.
```bash
# Running as a script
$ ./my_script.sh some args --blah
# Sourcing the script
$ source my_script.sh
$ my_script some more args --blah
```
(taken from the [bpkg](https://raw.githubusercontent.com/bpkg/bpkg/master/README.md) project)
## Todo
- [ ] Make `src` libs adhere to Best practices
- [ ] `make build` system for generating custom builds
- [ ] tests & releases via Travis
2013-03-27 16:08:31 +01:00
## License
2013-03-27 17:56:19 +01:00
Copyright (c) 2013 Kevin van Zonneveld, [http://kvz.io](http://kvz.io)
2013-03-28 14:23:24 +01:00
Licensed under MIT: [http://kvz.io/licenses/LICENSE-MIT](http://kvz.io/licenses/LICENSE-MIT)