shelp

shelp is a Git-based package manager for shell scripts written in Go.

Prerequisites

OS: Linux or macOS
git command installed

Supported Shells

Most POSIX compatible shells including Zsh. Tested on Bash & Zsh
fish shell

Installation

Install Binary

There are several ways to install shelp :

Homebrew or Linuxbrew (using Tap)
Download from GitHub releases
go get

Let's see in details.

Homebrew (Linuxbrew)

brew tap progrhyme/taps
brew install shelp

Download from releases

Download latest binary from GitHub releases and put it under one directory in $PATH entries.

Let's see typical commands to achieve this:

bin=/usr/local/bin  # Change to your favorite path
version=0.6.0       # Make sure this is the latest
os=darwin           # or "linux" is supported
curl -Lo $bin/shelp "https://github.com/progrhyme/shelp/releases/download/v${version}/shelp_${version}_${os}_x86_64"
chmod +x $bin/shelp

go get

Run the following:

go get github.com/progrhyme/shelp

Enable in Shell

To enable shelp automatically in your shell, append the following to your profile script (such as ~/.bashrc or ~/.zshrc):

# For POSIX-like shells
eval "$(shelp init -)"

As for fish shell, append the following to ~/.config/fish/config.fish:

# For fish shell
shelp init - | source

If you want to store shelp materials in a location different from the default ~/.shelp, set SHELP_ROOT environment variable beforehand.

See Configuration section for details and other options.

Quickstart

Install Packages

Command Syntax:

# Handy syntax using HTTPS protocol
shelp install [<site>/]<account>/<repository>[@<ref>] [<package>]

# Specify complete git-url with any protocol
shelp install <git-url> [<package>]

You can specify any branch or tag or commit hash for @<ref> parameter.

For example, the following command installs https://github.com/bats-core/bats-core into $SHELP_ROOT/packages/bats directory.

shelp install bats-core/bats-core bats

Then, you can run bats command in the package.

Other Examples:

# Handy syntax
shelp install b4b4r07/enhancd           # Install "enhancd" from github.com
shelp install b4b4r07/[email protected]    # Install specified tag or branch
shelp install gitlab.com/dwt1/dotfiles  # Install from gitlab.com

# Specify git-url
shelp install [email protected]:b4b4r07/enhancd.git  # Install via SSH protocol
shelp install file:///path/to/repository          # Install via Local protocol
shelp install git://server/gitproject.git         # Install via Git protocol

Limitation:

shelp install always clones repository as shallow one, with --depth=1 option.
You can't specify --branch option in the latter command syntax, nor others.

To specify every properties for packages, take a look at Configuration section.

Shell Function

The command eval "$(shelp init -)" (or shelp init - | source) loads a shell function include.

Function Usage:

include <package> <script-path>

This will load <script-path> in <package> by . shell built-in function.

For example, suppose you have installed https://github.com/ohmyzsh/ohmyzsh by shelp.
Then, the following command load oh-my-zsh.sh on your current shell:

include ohmyzsh oh-my-zsh.sh

NOTE:

In fish shell, source(1) command is used instead of . to load scripts

Configuration

There are some ways to configure shelp behavior:

Environment variables
Configuration file
Command-line options

Environment Variables

There are a few environment variables which shelp refers on running:

Variable	Default	Description
SHELP_CONFIG	`$SHELP_ROOT/config.yml`	Path of config file
SHELP_ROOT	`$HOME/.shelp`	Directory where the contents are stored

Configuration File

You do not necessarily need a configuration file to use shelp.
But it will give you a way to manage packages with the file.

Here is an example configuration:

packages:
- from: b4b4r07/[email protected]
- from: gitlab.com/dwt1/dotfiles
  as: dwt1-dotfiles
- from: bpkg/bpkg
  bin:
    - bpkg
- from: [email protected]:someone/gitproject.git
  at: feature/awesome

When you run shelp bundle with this configuration, the listed packages will be installed.

Take a look at example/config.yml to see available properties on configuration.

Command-line Options

-c|--config CONFIG option is available for all commands.
It specifies the path of configuration file and takes precedence over the environment variable SHELP_CONFIG.

CLI Usage

shelp COMMAND [arguments...] [options...]
shelp -h|--help          # Show general help
shelp COMMAND -h|--help  # Show help for COMMAND
shelp -v|--version       # Show CLI version

Available Commands

shelp init       # Initialize shelp for shell environment
shelp install    # Install a package
shelp add        # Alias of "install"
shelp remove     # Uninstall a package
shelp uninstall  # Alias of "remove"
shelp list       # List installed packages
shelp upgrade    # Upgrade installed packages
shelp outdated   # Show outdated packages
shelp link       # Pseudo installation of local directory
shelp bundle     # Install packages at once with config file
shelp prune      # Remove packages not defined in config file
shelp destroy    # Delete all materials including packages

Alternatives

There are othere tools to manage shell scripts in modular way.
Pick up some of them here.

Software	Supported Shells
basherpm/basher	Bash, Zsh, fish shell
zplug	Zsh
bpkg	Bash
jorgebucaran/fisher	fish shell

Special Thanks

basher inspired me to implement some features in this tool.

License

The MIT License.

# README