Shell Helpers

This is a collection of shell scripts/helpers I use. Works for bash and zsh

Installation

Clone the repository, then source the tools you want from ~/.bashrc or ~/.zshrc:

git clone https://github.com/leonbeon/shell-helpers.git "$HOME/shell-helpers"

source "$HOME/shell-helpers/docker/docker.sh"
source "$HOME/shell-helpers/mux/mux.sh"
source "$HOME/shell-helpers/mnt/mnt.sh"

For Oh My Bash or Oh My Zsh, clone the repository as a custom plugin instead:

# Oh My Bash
git clone https://github.com/leonbeon/shell-helpers.git "$HOME/.oh-my-bash/custom/plugins/shell-helpers"

# Oh My Zsh
git clone https://github.com/leonbeon/shell-helpers.git "$HOME/.oh-my-zsh/custom/plugins/shell-helpers"

Add shell-helpers to the end of the framework's plugins array so its commands take precedence over conflicting aliases:

plugins=(git shell-helpers)

Install Docker with the modern Compose plugin, tmux, and SSHFS separately as needed.

docker helpers

Docker helpers for operating containers directly and services in a Compose project. Commands honor COMPOSE_FILE or discover the nearest standard Compose file, then load permitted .env files from its directory and up to two parents, with nearer files taking precedence. Environment files at /, directly below /, or anywhere under /home are never inspected.

Command	Explanation	Example
dlogs [container]	Follows logs, resolving the local Compose container when omitted.	dlogs traefik
dbuild [service]	Builds one Compose service, resolving the local service when omitted.	dbuild web
drecreate [service]	Recreates one Compose service with --force-recreate.	drecreate web
dup [service]	Starts or updates one Compose service without forcing recreation.	dup web
drm [container]	Gracefully stops and removes a container.	drm traefik
dexec [-c container] [--] [command [arg ...]]	Runs a command in a container, or opens sh when no command is given.	dexec -c postgres psql -U postgres
drebuild [service]	Builds and then recreates one Compose service.	drebuild web

mux

A small tmux session helper for managing named sessions, typically one per project folder. It creates, attaches, lists, refreshes, and kills sessions, and must be run outside tmux. I usually use this to manage a tmux session per project folder.

Command	Explanation	Example
mux [session_name]	Attaches to or creates a session, defaulting to the current directory name.	mux website
mux --refresh <session_name>	Recreates or creates a named session in the current directory, which is useful for reloading shell environment variables.	mux --refresh website
mux --ls	Lists active tmux sessions.	mux --ls
mux --kill <session_name>	Kills a named session.	mux --kill website
mux --help	Prints the command summary.	mux --help

mnt

SSHFS helpers for mounting configured remote directories and safely unmounting them by shortcut or mount point.

Shortcuts live in ${XDG_CONFIG_HOME:-$HOME/.config}/mnt/mnt.conf:

[documents]
host = user@example.com
remote_path = /srv/documents
mount_point = /mnt/remote_documents

[media]
host = media-server
remote_path = /srv/media
mount_point = /mnt/remote_media

For mount points under /mnt, create the directory once and grant your user write access:

sudo mkdir -p /mnt/remote_documents
sudo chown "$(id -un):$(id -gn)" /mnt/remote_documents

Uncomment or add user_allow_other in /etc/fuse.conf because the helper uses SSHFS's allow_other option.

Command	Explanation	Example
mnt	Lists configured shortcuts and their state.	mnt
mnt <shortcut>	Mounts a configured SSHFS shortcut.	mnt documents
mnt <host> <remote_path> <mount_point>	Mounts an explicit SSHFS source.	mnt server /srv/documents /mnt/documents
mnt --help	Prints the mount command summary.	mnt --help
umnt	Lists active configured shortcuts.	umnt
umnt <shortcut_or_mount_point>	Unmounts an SSHFS mount by shortcut or path.	umnt documents
umnt --help	Prints the unmount command summary.	umnt --help

Note on AI use

I understand the complicated discussion around AI code in general. For my philosophy, having an AI agent write a semi-private productivity bash tool after having a focused discussion about the use cases with it is fine. This code is not meant to be state of the art or particularly pretty, it's short enough to at least take a glance at it and confirm it is not doing anything malicious, and this was not a one-shot either. AI commits are clearly marked via git author.