Some handy scripts to make your life easier.
All scripts were desgined to run in bash. Hum... right, You might ask about shebang... yes I used absolute path in all scripts '/bin/bash'. Yes, there is discussions on that matter, but if you plan to use it and don't use bash, you probably know some tricks to update all files at once, right? If not I will provide you a way to do that, if you have sed at least.
The scripts was designed thinking of a few baselines:
- Simplicity
- Reusability
- Meaningful reading
and the Unix concept of DOTADIW:
- Do One Thing And Do It Well
We designed a standard way for naming functions, which should start the function with the folder name, so, if the script is under the './domain' folder the function will start with 'domain_'. We try to be as much verbose as possible for better understanding "the function function".
The response from the functions will follow the function name which was called, for the 'check' functions the 'check' string will be removed in the reply, this way we can have a standard and the user will know the exact response from the function without a need to open and review it:
docker_check_container_is_running()
{
[...]
DOCKER_CONTAINER_IS_RUNNING=true
}The response has the same name of the function, but without the string 'check' and all capital letter.
***** GET FUNCIONS AS WELL
ip_get_external_ipv4 example returns IP_EXTERNAL_IPV4
Every change should be non breakable, if it worked for you in some main version it should continue to work in all corrections and new functions.
Versioning: vX.Y
'X': main version
'Y': corrections / new functions
There will be a specific page for documentation and samples of every function in this repo.
Please check