A collection of BASH utility functions and script templates used to ease the creation of portable and hardened BASH scripts with sane defaults.
There are two Script Templates located in the root level of this repository. The usage of these templates is described in detail below.
BASH Utility functions are located within the utilities/
folder.
Complex sed
find/replace operations are supported with the files located in sedfiles/
. Read the usage instructions.
Automated testing is provided using BATS. All tests are in the tests/
repo. A git pre-commit hook provides automated testing is located in the .hooks/
directory. Read about how to install the hook.
To create a new script, copy one of the script templates to a new file and make it executable chmod 755 [newscript].sh
. Place your custom script logic within the _mainScript_
function at the top of the script.
There are two templates located at the root level of this repository.
template.sh
- A lean template which attempts to source all the utility functions from this repository. You will need to update the path to the utilities folder sent to_sourceUtilities_
at the bottom of the script. This template will not function correctly if the utilities are not found.template_standalone.sh
- For portability, the standalone template does not assume that this repository is available. Copy and paste the individual utility functions under the### Custom utility functions
line.
The script templates are roughly split into three sections:
- TOP: Write the main logic of your script within the
_mainScript_
function. It is placed at the top of the file for easy access and editing. However, it is invoked at the end of the script after options are parsed and functions are sourced. - MIDDLE: Functions and default variable settings are located just below
_mainScript_
. - BOTTOM: Script initialization (BASH options, traps, call to
_mainScript_
, etc.) is at the bottom of the template
These default options and global variables are included in the templates and used throughout the utility functions. CLI flags to set/unset them are:
-h, --help
: Prints the contents of the_usage_
function. Edit the text in that function to provide help--logfile [FILE]
Full PATH to logfile. (Default is${HOME}/logs/$(basename "$0").log
)loglevel [LEVEL]
: Log level of the script. One of:FATAL
,ERROR
,WARN
,INFO
,DEBUG
,ALL
,OFF
(Default is 'ERROR
')-n, --dryrun
: Dryrun, sets$DRYRUN
totrue
allowing you to write functions that will work non-destructively using the_execute_
function-q, --quiet
: Runs in quiet mode, suppressing all output to stdout. Will still write to log files-v, --verbose
: Sets$VERBOSE
totrue
and prints all debug messages to stdout--force
: If using the_seekConfirmation_
utility function, this skips all user interaction. ImpliedYes
to all confirmations.
You can add custom script options and flags to the _parseOptions_
function.
The bottom of the script template file contains a block which initializes the script. Comment, uncomment, or change the settings here for your needs
trap '_trapCleanup_ ${LINENO} ${BASH_LINENO} "${BASH_COMMAND}" "${FUNCNAME[*]}" "${0}" "${BASH_SOURCE[0]}"' EXIT INT TERM SIGINT SIGQUIT SIGTERM ERR
# Trap errors in subshells and functions
set -o errtrace
# Exit on error. Append '||true' if you expect an error
set -o errexit
# Use last non-zero exit code in a pipeline
set -o pipefail
# Confirm we have BASH greater than v4
[ "${BASH_VERSINFO:-0}" -ge 4 ] || {
printf "%s\n" "ERROR: BASH_VERSINFO is '${BASH_VERSINFO:-0}'. This script requires BASH v4 or greater."
exit 1
}
# Make `for f in *.txt` work when `*.txt` matches zero files
shopt -s nullglob globstar
# Set IFS to preferred implementation
IFS=$' \n\t'
# Run in debug mode
# set -o xtrace
# Source utility functions
_sourceUtilities_
# Initialize color constants
_setColors_
# Disallow expansion of unset variables
set -o nounset
# Force arguments when invoking the script
# [[ $# -eq 0 ]] && _parseOptions_ "-h"
# Parse arguments passed to script
_parseOptions_ "$@"
# Create a temp directory '$TMP_DIR'
# _makeTempDir_ "$(basename "$0")"
# Acquire script lock
# _acquireScriptLock_
# Source GNU utilities for use on MacOS
# _useGNUUtils_
# Run the main logic script
_mainScript_
# Exit cleanly
_safeExit_
The files within utilities/
contain BASH functions which can be used in your scripts. Each included function includes detailed usage information. Read the inline comments within the code for detailed usage instructions.
Within the utilities
folder are many BASH functions meant to ease development of more complicated scripts. These can be included in the template in two ways.
You can copy any complete function from the Utilities and place it into your script. Copy it beneath the ### Custom utility functions
line. Scripts created this way are fully portable among systems
template.sh
contains a function to source all the utility files into the script. Beware, that you'll need to update the paths within the _sourceUtilities_
function to ensure your script can find this repository.
_columnizeOutput_
Creates a column output for key/value pairs with line wrapping for the right column (value)- -
_printFuncStack_
Prints the function stack in use. Used for debugging, and error reporting _alert_
Performs alerting functions including writing to a log file and printing to screen_centerOutput_
Prints text in the center of the terminal window_setColors_
Sets color constants for alerting (Note: Colors default to a dark theme.)
Basic alerting, logging, and setting color functions (included in scriptTemplate.sh
by default). Print messages to stdout and to a user specified logfile using the following functions.
debug "some text" # Printed only when in verbose (-v) mode
info "some text" # Basic informational messages
notice "some text" # Messages which should be read. Brighter than 'info'
warning "some text" # Non-critical warnings
error "some text" # Prints errors and the function stack but does not stop the script.
fatal "some text" # Fatal errors. Exits the script
success "some text" # Prints a success message
header "some text" # Prints a header element
dryrun "some text" # Prints commands that would be run if not in dry run (-n) mode
The following global variables must be set for the alert functions to work
$DEBUG
- Iftrue
, printsdebug
level alerts to stdout. (Default:false
)$DRYRUN
- Iftrue
does not eval commands passed to_execute_
function. (Default:false
)$LOGFILE
- Path to a log file$LOGLEVEL
- One of: FATAL, ERROR, WARN, INFO, DEBUG, ALL, OFF (Default:ERROR
)$QUIET
- Iftrue
, prints to log file but not stdout. (Default:false
)
Utility functions for working with arrays.
_dedupeArray_
Removes duplicate array elements_forEachDo_
Iterates over elements and passes each to a function_forEachFilter_
Iterates over elements, returning only those that are validated by a function_forEachFind_
Iterates over elements, returning the first value that is validated by a function_forEachReject_
Iterates over elements, returning only those that are NOT validated by a function_forEachValidate_
Iterates over elements and passes each to a function for validation_inArray_
Determine if a value is in an array_isEmptyArray_
Checks if an array is empty_joinArray_
Joins items together with a user specified separator_mergeArrays_
Merges the values of two arrays together_randomArrayElement_
Selects a random item from an array_reverseSortArray_
Sorts an array from highest to lowest_setdiff_
Return items that exist in ARRAY1 that are do not exist in ARRAY2_sortArray_
Sorts an array from lowest to highest
Functions for validating common use-cases
_commandExists_
Check if a command or binary exists in the PATH_functionExists_
Tests if a function is available in current scope_isInternetAvailable_
Checks if Internet connections are possible_isAlpha_
Validate that a given variable contains only alphabetic characters_isAlphaDash_
Validate that a given variable contains only alpha-numeric characters, as well as dashes and underscores_isAlphaNum_
Validate that a given variable contains only alpha-numeric characters_isDir_
Validate that a given input points to a valid directory_isEmail_
Validates that an input is a valid email address_isFQDN_
Determines if a given input is a fully qualified domain name_isFile_
Validate that a given input points to a valid file_isIPv4_
Validates that an input is a valid IPv4 address_isIPv6_
Validates that an input is a valid IPv6 address_isNum_
Validate that a given variable contains only numeric characters_isTerminal_
Checks if script is run in an interactive terminal_rootAvailable_
Validate we have superuser access as root (via sudo if requested)_varIsEmpty_
Checks if a given variable is empty or null_varIsFalse_
Checks if a given variable is false_varIsTrue_
Checks if a given variable is true
Functions for working with dates and time.
_convertToUnixTimestamp_
Converts a date to unix timestamp_countdown_
Sleep for a specified amount of time_dateUnixTimestamp_
Current time in unix timestamp_formatDate_
Reformats dates into user specified formats_fromSeconds_
Convert seconds to HH:MM:SS_monthToNumber_
Convert a month name to a number_numberToMonth_
Convert a month number to its name_parseDate_
Takes a string as input and attempts to find a date within it to parse into component parts (day, month, year)_readableUnixTimestamp_
Format unix timestamp to human readable format_toSeconds_
Converts HH:MM:SS to seconds
Functions to aid in debugging BASH scripts
_pauseScript_
Pause a script at any point and continue after user input_printAnsi_
Helps debug ansi escape sequence in text by displaying the escape codes_printArray_
Prints the content of array as key value pairs for easier debugging
Functions for working with files.
_backupFile_
Creates a backup of a specified file with .bak extension or optionally to a specified directory._decryptFile_
Decrypts a file withopenssl
_encryptFile_
Encrypts a file withopenssl
_extractArchive_
Extract a compressed file_fileBasename_
Gets the basename of a file from a file name_fileContains_
Tests whether a file contains a given pattern_filePath_
Gets the absolute path to a file_fileExtension_
Gets the extension of a file_fileName_
Prints a filename from a path_json2yaml_
Convert JSON to YAML uses python_listFiles_
Find files in a directory. Use either glob or regex._makeSymlink_
Creates a symlink and backs up a file which may be overwritten by the new symlink. If the exact same symlink already exists, nothing is done._parseYAML_
Convert a YAML file into BASH variables for use in a shell script_printFileBetween_
Prints block of text in a file between two regex patterns_readFile_
Prints each line of a file_sourceFile_
Source a file into a script_createUniqueFilename_
Ensure a file to be created has a unique filename to avoid overwriting other files_yaml2json_
Convert a YAML file to JSON with python
Functions useful when writing scripts to be run on macOS
_guiInput_
Ask for user input using a Mac dialog box_haveScriptableFinder_
Determine whether we can script the Finder or not_homebrewPath_
Adds Homebrew bin directory to PATH_useGNUUtils_
Add GNU utilities to PATH to allow consistent use of sed/grep/tar/etc. on MacOS
Miscellaneous functions
_acquireScriptLock_
Acquire script lock to prevent running the same script a second time before the first instance exits_detectLinuxDistro_
Detects the host computer's distribution of Linux_detectMacOSVersion_
Detects the host computer's version of macOS_detectOS_
Detect the the host computer's operating system_endspin_
Clears output from the spinner_execute_
Executes commands with safety and logging options. RespectsDRYRUN
andVERBOSE
flags._findBaseDir_
Locates the real directory of the script being run. Similar to GNU readlink -n_generateUUID_
Generates a unique UUID_progressBar_
Prints a progress bar within a for/while loop_runAsRoot_
Run the requested command as root (via sudo if requested)_seekConfirmation_
Seek user input for yes/no question_spinner_
Creates a spinner within a for/while loop._trapCleanup_
Cleans up after a trapped error.
Functions to work with external services
_haveInternet_
Tests to see if there is an active Internet connection_httpStatus_
Report the HTTP status of a specified URL_pushover_
Sends a notification via Pushover (Requires API keys)
Functions for string manipulation
_cleanString_
Cleans a string of text_decodeHTML_
Decode HTML characters with sed. (Requires sed file)_decodeURL_
Decode a URL encoded string_encodeHTML_
Encode HTML characters with sed (Requires sed file)_encodeURL_
URL encode a string_escapeString_
Escapes a string by adding\
before special chars_lower_
Convert a string to lowercase_ltrim_
Removes all leading whitespace (from the left)_regexCapture_
Use regex to validate and parse strings_rtrim_
Removes all leading whitespace (from the right)_splitString_
Split a string based on a given delimeter_stringContains_
Tests whether a string matches a substring_stringRegex_
Tests whether a string matches a regex pattern_stripANSI_
Strips ANSI escape sequences from text_stripStopwords_
Removes common stopwords from a string using a list of sed replacements located in an external file._trim_
Removes all leading/trailing whitespace_upper_
Convert a string to uppercase
Functions required to allow the script template and alert functions to be used
_makeTempDir_
Creates a temp directory to house temporary files_safeExit_
Cleans up temporary files before exiting a script_setPATH_
Add directories to $PATH so script can find executables
- Function names use camel case surrounded by underscores:
_nameOfFunction_
- Local variable names use camel case with a starting underscore:
_localVariable
- Global variables are in ALL_CAPS with underscores seperating words
- Exceptions to the variable an function naming rules are made for alerting functions and colors to ease my speed of programming. (Breaking years of habits is hard...) I.e.
notice "Some log item: ${blue}blue text${reset}
Wherenotice
is a function and$blue
and$reset
are global variables but are lowercase. - Variables are always surrounded by quotes and brackets
"${1}"
(Overly verbose true, but a safe practice) - Formatting is provided by shfmt using 4 spaces for indentation
- All scripts and functions are fully Shellcheck compliant
- Where possible, I follow defensive BASH programming principles.
I compiled these scripting utilities over many years without having an intention to make them public. As a novice programmer, I have Googled, GitHubbed, and StackExchanged a path to solve my own scripting needs. I often lift a function whole-cloth from a GitHub repo don't keep track of its original location. I have done my best within these files to recreate my footsteps and give credit to the original creators of the code when possible. Unfortunately, I fear that I missed as many as I found. My goal in making this repository public is not to take credit for the code written by others. If you recognize something that I didn't credit, please let me know.
MIT