bash3boilerplate
bash-oo-framework
bash3boilerplate | bash-oo-framework | |
---|---|---|
5 | 5 | |
2,170 | 5,601 | |
0.1% | 0.0% | |
3.1 | 0.0 | |
9 months ago | over 1 year ago | |
Shell | Shell | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bash3boilerplate
-
Techniques I Use to Create a Great User Experience for Shell Scripts
I can highly recommend using bash3boilerplate (https://github.com/kvz/bash3boilerplate) if you're writing BASH scripts and don't care about them running on systems that don't use BASH.
It provides logging facilities with colour usage for the terminal (not for redirecting out to a file) and also decent command line parsing. It uses a great idea to specify the calling parameters in the help/usage information, so it's quick and easy to use and ensures that you have meaningful information about what parameters the script accepts.
Also, please don't write shell scripts without running them through ShellCheck. The shell has so many footguns that can be avoided by correctly following its recommendations.
-
Being a bash developer in the 21st century
I'm a fan of Bash3 Boilerplate (https://github.com/kvz/bash3boilerplate) and use a modified version of it for my shell scripts now. I like the code style and the logging, although I've amended the logging slightly to add a pipe input for long running processes that you want to see the output from before it finishes.
I prefer having a stop-on-unexpected script as it makes errors far more explicit and it's not too onerous to work round the peculiarities of return codes.
Greg's wiki (https://mywiki.wooledge.org/) is my go to resource for looking up snippets and learning to avoid the footguns - that and shellcheck are the key to "robust" bash scripts.
- Bashkit V1
- BashLib a helpful source file for any script
-
How do you add logs in your bash scripts?
Inspired from https://github.com/kvz/bash3boilerplate/blob/master/main.sh
bash-oo-framework
- Bashkit V1
-
I will never use sepples
Behold! OOP Bash! https://github.com/niieani/bash-oo-framework
- BashLib a helpful source file for any script
-
Examples of cool || non-standard || "simply insane" bash stuff?
https://github.com/niieani/bash-oo-framework - oo principals implemented in bash
-
Something equivalent to classes in bash?
Otherwise... maybe this?
What are some alternatives?
bash-commons - A collection of reusable Bash functions for handling common tasks such as logging, assertions, string manipulation, and more
awesome-shell - A curated list of awesome command-line frameworks, toolkits, guides and gizmos. Inspired by awesome-php.
ansi - ANSI escape codes in pure bash - change text color, position the cursor, much more
pure-bash-bible - 📖 A collection of pure bash alternatives to external processes.
events - An event/callback/promise system for bash apps that's fast (10k/s), tiny (<2.2K), and portable (bash 3.2+, builtins-only)
shournal - Log shell-commands and used files. Snapshot executed scripts. Fully automatic.