Forked from jazik/termenv.

TermForge is an Ansible playbook that forges a full-featured terminal environment on Linux and macOS hosts. It keeps the original termenv spirit while adding macOS polish, automatic iTerm2 setup, and Kubernetes helper tooling that lights up as soon as kubectl is in your PATH.

• Shell stack – zsh, oh-my-zsh, Powerlevel10k, color + autosuggest plugins, and curated defaults.
• Terminal UX – tmux with a powerline theme, fzf, custom keymaps, and smart Neovim ↔ tmux navigation glue.
• Editor batteries – Neovim + Lua config, Telescope/Ripgrep, Treesitter, Copilot(optional), and CSpell ready to go.
• Fonts + UI – Nerd Fonts installer, macOS font placement, automatic iTerm2 install via Homebrew Cask.
• Kubernetes helpers – k9s, kubectx, and kubens automatically installed when kubectl is detected.

Inspired by:

• Terminal History Auto Suggestions As You Type With Oh My Zsh
• bcampolo/nvim-starter-kit

Run the playbook with a user that has sudo privileges.

sudo dnf install git ansible

sudo apt-get update
sudo apt-get install git ansible

Install Command Line Tools and Homebrew, then install Ansible and Git:

xcode-select --install
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
brew install ansible git

Homebrew is also required so TermForge can install zsh, tmux, node, k9s, kubectx, kubens, and iTerm2.

Heads-up: On Apple Silicon you might see an interpreter-discovery warning similar to /opt/homebrew/bin/python3.14. This is harmless, but you can silence it by exporting ANSIBLE_PYTHON_INTERPRETER=/opt/homebrew/bin/python3 (or by setting ansible_python_interpreter in hosts).

git clone https://github.com/<your-user>/termforge.git
cd termforge
ansible-playbook -i hosts --ask-become-pass termforge.yml

The legacy termenv.yml playbook now just imports termforge.yml, so existing scripts keep working while you migrate.

All roles are enabled by default. Use tags to skip or run a subset:

ansible-playbook -i hosts termforge.yml --skip-tags tmux
ansible-playbook -i hosts termforge.yml --tags "neovim,k8s-tools"

Tag names match the role names (see termforge.yml).

The nerd-fonts tag installs the latest Fira Mono Nerd Font by default. To install another Nerd Font:

ansible-playbook -i hosts nerdfonts.yml -e "font_name=YourFontName"

The YourFontName value is the Nerd Font zip filename without .zip. See the Nerd Fonts download page.

On macOS fonts land in ~/Library/Fonts/<FontName> and are immediately available, so fc-cache is not required.

When TermForge runs on macOS it automatically applies the iterm2 tag and installs iTerm2 via Homebrew Cask. You can still target or skip the role:

ansible-playbook -i hosts termforge.yml --skip-tags iterm2
ansible-playbook -i hosts termforge.yml --tags iterm2

After provisioning:

• Launch iTerm2 → Preferences → Profiles → Text and select the Nerd Font you installed (Fira Mono Nerd Font by default).
• Toggle Use ligatures if you want stylistic glyphs.
• If you sync settings, open Preferences → General → Preferences and point it to your sync folder before rerunning the playbook.

The kubernetes-tools role installs k9s, kubectx, and kubens whenever kubectl is already available. Nothing is installed if kubectl is missing, so your environment stays lean until you actually use Kubernetes.

Copilot/CopilotChat are optional to avoid noisy errors on fresh systems. To add them later:

ansible-playbook -i hosts neovim-copilot.yml

Use the Dockerfile to spin up a disposable TermForge shell.

docker build -t termforge . --build-arg DISTRO=fedora
docker build -t termforge . --build-arg DISTRO=ubuntu
docker run --rm -it termforge
docker run --rm -it -v .:/home/termforge/termforge:Z termforge

Install vagrant, plus libvirt and VirtualBox providers if you plan to use them.

Fedora quick-start (VirtualBox requires RPMFusion):

sudo dnf install vagrant vagrant-libvirt VirtualBox libvirt
sudo usermod -a -G libvirt ${USER}

Allow NFS inside the libvirt firewall zone when using Fedora:

sudo systemctl --now enable virtnetworkd.service
sudo firewall-cmd --permanent --zone=libvirt --add-service=nfs
sudo firewall-cmd --reload

Vagrantfile exposes Fedora and Ubuntu definitions with a few handy flags:

vagrant [--local=no|yes] [--do-install=yes|no] <command> [fedora|ubuntu]

--local       Run playbook from GitHub (no, default) or locally (yes)
--do-install  Install dependencies on the guest (yes, default) or skip (no)
<command>     Standard vagrant verbs (up, destroy, ssh, ...)
fedora|ubuntu Target one distro; omit to manage both

Example (local Fedora test run):

vagrant --local=yes up fedora
vagrant ssh fedora
vagrant destroy fedora

Provisioning fails fast if the Ansible run fails, so verify the resulting environment manually after the VM boots.