ebash
enhanced bash (by elibs)
bash-commons
A collection of reusable Bash functions for handling common tasks such as logging, assertions, string manipulation, and more (by gruntwork-io)
| ebash | bash-commons | |
|---|---|---|
| 2 | 3 | |
| 14 | 725 | |
| - | 0.8% | |
| 6.0 | 2.6 | |
| about 1 month ago | about 1 month ago | |
| Shell | Shell | |
| Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
ebash
Posts with mentions or reviews of ebash.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-27.
- Bashkit V1
-
lobash: a modern, safe, powerful library for Bash script development
You should take a look at ebash https://github.com/elibs/ebash
bash-commons
Posts with mentions or reviews of bash-commons.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-27.
- Bashkit V1
- BashLib a helpful source file for any script
-
How to structure library?
I think I phrased what I said poorly and unintentially communicated that I want to have all my code in one file. that' the opposite of what I'm wanting. To clarify, and I know this is splitting hairs but it illustrates my point. I think this log shell file is a good example of what I want to NOT do with my library. instead of having one file with 5 functions, I think it should be 5 files with no functions. that's to say the new file "log_info" would contain this text:
What are some alternatives?
When comparing ebash and bash-commons you can also consider the following projects:
lobash - A modern, safe, powerful utility/library for Bash script development.
bashkit - Official bashkit repository
bash-utility - Bash library which provides utility functions and helpers for functional programming in Bash.
basher - A package manager for shell scripts.
Conky - A private place for my conky widget
balls - Bash on Balls
mo - Mustache templates in pure bash
awesome-bash - A curated list of delightful Bash scripts and resources.
bash-it - A community Bash framework.
bash-oo-framework - Bash Infinity is a modern standard library / framework / boilerplate for Bash
bash3boilerplate - Templates to write better Bash scripts