Small shell helpers for everyday developer work. Each plugin lives in its own
folder under plugins/ and works in zsh and bash unless noted.
| Plugin | What it does |
|---|---|
| cfuse | Several Cloud Foundry logins side by side, switch with cfuse <name> |
curl -fsSL https://raw.githubusercontent.com/operayo/shell-plugins/main/install.sh | bashThis clones the repo to ~/.shell-plugins (override with SHELL_PLUGINS_DIR)
and installs all plugins. For specific plugins only: … | bash -s cfuse.
Or from your own clone: git clone https://github.com/operayo/shell-plugins.git && ./shell-plugins/install.sh
What the installer does, per plugin:
- oh-my-zsh: links the plugin into
$ZSH_CUSTOM/plugins/and tells you to add its name toplugins=(...)in~/.zshrc - zsh without oh-my-zsh: adds a marked
sourceline to~/.zshrc - bash (if
~/.bashrcexists or bash is your shell): adds a markedsourceline to~/.bashrc - config: copies
<file>.exampleto~/.config/<plugin>/<file>if it doesn't exist yet
Re-running it is safe. Run it again after moving your clone, and it fixes the
paths. To update: run the curl line again, or git pull in your clone.
To uninstall: remove the plugin from plugins=(...) / delete the lines marked
# shell-plugins:<name> from your rc files.
plugins/<name>/
├── <name>.sh # shared logic, bash + zsh compatible
├── <name>.plugin.zsh # zsh entry: sources <name>.sh, adds completion
├── <name>.bash # bash entry: sources <name>.sh, adds completion
├── <file>.example # optional, installed to ~/.config/<name>/<file>
└── README.md
install.sh picks up new plugin folders automatically.
Keep personal settings (endpoints, names, tokens) out of the repo — read them
from a config file under ~/.config/<name>/ instead.
Madhusudhanan Perumalswamy (@mperumalswamy)
MIT © operayo GmbH