- Clone
- Install Dependencies
- Add to
$PATH - Link Configs and Inherit Bash Environment and
$PATH - Import just the
$PATH
mkdir -p -v ~/github
git clone https://github.com/HariSekhon/DevOps-Bash-tools ~/github/bash-toolsThen run make to install any dependencies, system packages, libraries etc.
If you only want to use a specific script you could skip this setp and install bits yourself,
possibly using the install/install*.sh scripts.
cd ~/github/bash-toolsmakeOR install only the individual bits you need for a specific script you want to run:
install/install_aws_cli.shinstall/install_gcloud_sdk.shinstall/install_homebrew.sh
brew install jqNow run whichever script you came for...
Much of the rest of this knowledge base gives the short script names for brevity.
You should add the directories containing the scripts to your $PATH.
You can do this manually or by automatically linking
The configs/ directory is full of dotfiles that get symlinked to your $HOME directory if you run this at the root
of the repo:
make linkAny existing configs get skipped for safety.
The output will show what is symlinked and what is skipped.
Any ~/.bash* or ~/.zsh* files will have a source line added which will include all the aliases,
functions and paths to the subdirectories of the repo containing the many scripts.
If you'd rather not import everything,
you can just source the .bash.d/paths.sh yourself in your ~/.bashrc by adding this:
source ~/github/bash-tools/.bash.d/paths.sh