SSH wrapper that transfers and sources your local dotfiles to remote sessions without requiring installation on the remote host.
Kyrat is an SSH wrapper script that transfers and sources your local dotfiles (bashrc, vimrc, inputrc, tmux.conf, zshrc) to remote SSH sessions. It solves the problem of inconsistent shell environments when working across multiple servers by bringing your personalized configuration with you without requiring any installation on remote hosts.
System administrators, DevOps engineers, and developers who frequently SSH into multiple remote servers and want to maintain a consistent shell environment across all their sessions.
Kyrat provides a lightweight, zero-installation solution for dotfile synchronization that works without root access on remote hosts, unlike alternatives that require package installation or complex setup procedures on each server.
SSH wrapper script that brings your dotfiles always with you on Linux and OSX
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Requires no software installation or root access on remote hosts, as dotfiles are encoded and passed via ssh command line, making it ideal for shared or restricted servers.
Uses Base64 encoding and Gzip compression to obfuscate dotfiles during transfer, and automatically removes them from remote /tmp directories on session exit, enhancing security.
Allows spawning bash, zsh, or sh shells remotely via the KYRAT_SHELL environment variable, accommodating different user preferences without remote configuration.
Works on both Linux and macOS systems, enabling consistent dotfile usage across different local machines, as highlighted in the platform-specific installation instructions.
Only supports bashrc, vimrc, inputrc, tmux.conf, and zshrc, excluding common configuration files like .gitconfig or .profile, which limits its utility for full environment synchronization.
Requires bash >=4.0 and GNU coreutils, with manual installation via git clone and PATH export—no package manager support—making setup more complex than drop-in solutions.
The README's troubleshooting section is intentionally left blank, offering no guidance for resolving potential problems, which could frustrate users encountering errors.