https://github.com/joknarf/thefly
shell teleporter plugin manager (bash/zsh/ksh)
https://github.com/joknarf/thefly
bash ksh multihost multiuser plugin-manager shell shell-environment ssh sudo teleportation zsh
Last synced: about 2 months ago
JSON representation
shell teleporter plugin manager (bash/zsh/ksh)
- Host: GitHub
- URL: https://github.com/joknarf/thefly
- Owner: joknarf
- License: mit
- Created: 2024-09-15T22:10:04.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-10-20T18:32:51.000Z (4 months ago)
- Last Synced: 2025-10-20T19:06:47.187Z (4 months ago)
- Topics: bash, ksh, multihost, multiuser, plugin-manager, shell, shell-environment, ssh, sudo, teleportation, zsh
- Homepage: https://joknarf.github.io/joknarf-tools
- Size: 86.9 KB
- Stars: 8
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://joknarf.github.io/joknarf-tools)
[]()
[]()
[](https://shields.io/)
# thefly
bash/zsh/ksh plugin manager and env teleporter
Your shell env and plugins are available everywhere (hosts/users)
bzzz bzzz !
## Demo
## Install
```
. <(curl https://raw.githubusercontent.com/joknarf/thefly/main/thefly) install
```
or
```
$ git clone https://github.com/joknarf/thefly
$ . thefly/thefly install
```
Creates ~/.fly.d/fly and activate thefly manager for current user
or use your prefered method according to your OS:
```
brew install joknarf/tools/thefly
```
```
sudo dnf install https://github.com/joknarf/thefly/releases/latest/download/thefly.rpm
```
```
curl -OL https://github.com/joknarf/thefly/releases/latest/download/thefly.deb
sudo dpkg -i thefly.deb
```
```
curl -OL https://github.com/joknarf/thefly/releases/latest/download/thefly.apk
sudo apk add --allow-untrusted thefly.apk
```
```
curl -OL https://github.com/joknarf/thefly/releases/latest/download/thefly.pkg
sudo installer -pkg thefly.pkg -target /
```
then run:
```
thefly install
. ~/.fly.d/activate
```
Add in your rc file (.profile .bash_profile .bashrc .zshrc):
```
. ~/.fly.d/fly source
```
Get some help
```
fly help
```
## Add plugins
```
fly add joknarf/redo
```
clones `https://github.com/joknarf/redo` in `~/.fly.d/plugins/redo` and sources the `plugin.`
(all plugins in `~/fly.d/plugins/*/*.plugin.` will be sourced at login with `fly source` in your shell rc file)
## Teleport plugins/shell env
* To another user on current host
```
$ flyas
or
$ fsu
```
will duplicate `~/.fly.d` (without cvs files/tests) in `/tmp/.fly.//.fly.d` and source all plugins
by default uses `` shell, to force your favorite shell:
`fsub` or `bsu` (bash) - `fsuz` or `zsu` (zsh) - `fsuk` or `ksu` (ksh)
* To another host/user
```
$ flyto [] [<@host>]
or
$ fssh [] [<@host>]
```
will duplicate `~/.fly.d` (without cvs files/tests) in `:/tmp/.fly.//.fly.d` and source all plugins
by default uses `` shell, to force your favorite shell:
`fsshb` or `bto` (bash) - `fsshz` or `zto` (zsh) - `fsshk` or `kto` (ksh)
* To another shell
Change current shell and load your env/plugins:
`$ flysh # shell in bash ksh zsh`
or `fbash` - `fzsh` - `fksh`
## Customize env
Putting your env in `~/.fly.d/.flyrc` will be automatically sourced (must be compatible with different shells)
Putting additional shell specific env in `~/.fly.d/.rc` (.bashrc/.kshrc/.zshrc), will be automatically sourced for shell.
anything in `~.fly.d` will be available through ssh/sudo (flyto/flyas) in `$FLY_HOME/.fly.d`
For example, just put your `.vimrc` in `~/.fly.d` and add in `~/.fly.d/.flyrc`:
```
export VIMINIT="source $FLY_HOME/.fly.d/.vimrc"
```
same for `.inputrc`, put it in `~/.fly.d` and add in `~/.fly.d/.flyrc`:
```
export INPUTRC="$FLY_HOME/.fly.d/.inputrc"
```
You can crate a `.fly.d/bin` directory and put scripts you want to teleport and add in your `.fly.d/.flyrc`:
```
export PATH="$PATH:$FLY_HOME/.fly.d/bin"
```
## Create your standalone fly package with your full shell env/plugins
Save your whole shell environment to use everywhere with standalone fly package.
All your ~/.fly.d environment saved in autoextractable file. The fly package enables your env when sourced.
Build your fly package (you can copy and use it directly to get your env or make it available on web server to remote download)
```
$ flypack >fly.pak
$ scp fly.pak myhost:
$ . ./fly.pak source
```
load your env in current user (can be put in your .bashrc/.zshrc/.kshrc):
```
$ . <(curl -sL https://raw.githubusercontent.com/joknarf/flypack/main/fly.pak) source
```
install on current user in `~/.fly.d`:
```
$ . <(curl -sL https://raw.githubusercontent.com/joknarf/flypack/main/fly.pak) install
```
to connect to a server with your env in `/tmp/.fly.$USER`, use for example:
```
$ ssh -t '. <(curl -sL https://raw.githubusercontent.com/joknarf/flypack/main/fly.pak) [bash|ksh|zsh]'
```
Connect to all servers with your fly pak with ssh config:
```
RequestTTY yes
RemoteCommand . <(curl -sL https://raw.githubusercontent.com/joknarf/flypack/main/fly.pak)
```
## Download/activate your env/plugins from your fly git repo or web server
put your .fly.d directory into a git repo and activate all your env/plugins in your current user
```
. <(curl https://raw.githubusercontent.com/joknarf/thefly/main/thefly) install joknarf/myfly
```
create a tgz file with your .fly.d exposed on web server and activate env/plugins in your current user
```
. <(curl https://raw.githubusercontent.com/joknarf/thefly/main/thefly) install https://myserver/myfly
```
## Connect using thefly env/plugins from http/git repo
uses user ~.fly.d to load env/plugins
```
$ ssh -t @ '. <(curl https://raw.githubusercontent.com/joknarf/thefly/main/thefly) remote'
```
get env/plugins from .fly.d tgz (contains .fly.d/*)
```
$ ssh -t @ '. <(curl https://raw.githubusercontent.com/joknarf/thefly/main/thefly) remote '
```
get env/plugins from github repository (repo contains .fly.d contents, and can contain plugins submodules)
```
$ ssh -t @ '. <(curl https://raw.githubusercontent.com/joknarf/thefly/main/thefly) remote '
```
## Set your joknarf cool plugins env
```
$ fly add joknarf/nerdp # bash/ksh/zsh nerd prompt
$ fly add joknarf/seedee # bash/ksh/zsh cd history
$ fly add joknarf/redo # bash/zsh command history
$ fly add joknarf/complete-ng # bash/zsh completion next-gen
or just add the optimized compilation of these shell plugins using just:
$ fly add joknarf/shell-ng
$ fly add joknarf/pgtree # bash/ksh/zsh process hierarchy
$ fly add joknarf/lsicon # ls enhancer (colors/icons)
$ fly add joknarf/dfbar # df enhancer (colors/usage bar)
```
|link |description |
|-----------------------------------------------------|------------------------------------------------------------------------|
|[nerdp](https://github.com/joknarf/nerdp) |nerd dynamic customizable nice prompt |
|[seedee](https://github.com/joknarf/seedee) |access/search dir history with ctrl or shift down arrow, and many more |
|[redo](https://github.com/joknarf/redo) |access/search shell history command menu with shift-tab, and many more |
|[complete-ng](https://github.com/joknarf/complete-ng)|autocompletion with interactive menu |
|__[shell-ng](https://github.com/joknarf/shell-ng)__ |__optimized joknarf compilation of the above plugins__ |
|[pgtree](https://github.com/joknarf/pgtree) |process search / tree / kill command line |
|[lsicon](https://github.com/joknarf/lsicon) |ls command enhancer (colors/icons) |
|[dfbar](https://github.com/joknarf/dfbar) |df command enhancer (colors/usage bar) |
## Don't teleport a human with your fly !
Remember that ~/.fly.d directory will be duplicated in /tmp when teleporting, don't put huge data in your ~/.fly.d directory, the consequences could be dramatic ! (ask Jeff G. ;-)
Bzzz Bzzz