envira

Set up a development machine from a declarative catalog: zsh with oh-my-zsh and the mzz-ys theme, language toolchains (Rust, Go, Node.js, Python), modern terminal tools, editors, coding agents and monitors. About 100 tools and 20 configs.

envira shows what is installed, missing, outdated or drifted, installs what is missing with its dependencies, updates tools in place, and applies or reverts configs. It runs as a TUI or as plain commands for scripts and Dockerfiles.

• Linux x86_64 and aarch64: Ubuntu/Debian, Fedora/RHEL, Arch/Manjaro, openSUSE. A single static binary with no dependencies.
• macOS on Apple Silicon, with Homebrew.
• With or without sudo: without it, envira picks user-scope routes.

Install

# install into ~/.local/bin (checks its SHA-256) and open envira
curl -fsSL https://boot.controlnet.space/envira | bash
# install and run a command instead, e.g. in a Dockerfile or CI (no terminal needed)
curl -fsSL https://boot.controlnet.space/envira | bash -s -- install full -y
# or from PyPI
pipx install envira        # or: uv tool install envira
# or from crates.io: the release binary, or a build from source (Rust 1.93+ and a C compiler)
cargo binstall envira      # or: cargo install --locked envira

envira self-update updates envira itself, the same way it was installed (release binary, pipx, uv, pip or cargo). envira mentions a newer release after commands and in the TUI header (U there updates it); it never updates on its own. ENVIRA_NO_UPDATE_CHECK=1 turns the check off, and it is skipped in CI.

Use

envira                     # the TUI: pick bundles, review the plan, watch it run
envira status              # what is installed, missing, outdated or drifted
envira install full        # a bundle: installs it, and this machine keeps it
envira install             # later: whatever the kept bundles miss (new catalog items too)
envira install bat yazi    # some tools or configs, with their dependencies (not kept)
envira plan                # what `envira install` would do, without doing it
envira update              # update outdated tools in place
envira retry               # retry what failed or was blocked in the last run
envira self-update         # update envira itself (--check, --version 0.1.1 to go back)
envira log / explain <id>  # logs of the last run; why an item has its status
envira doctor              # machine facts, catalog layers, PATH, shell integration

Before anything runs, the plan lists each step, why it is there, and the exact commands:

A failed step only blocks what depends on it. Network failures are retried, and r (or envira retry) runs what is left once the cause is fixed:

Bundles (envira install <bundle>):

• With sudo, packages go system-wide; without it, envira picks user-scope routes. When a plan needs sudo and sudo asks for a password, envira asks for it before the plan runs (in the TUI, a dialog over the plan), with Use user mode next to it: the plan made again without sudo. Items that have a user-scope route take it (bat from its GitHub release into ~/.local/bin instead of apt), the others are left out, and no password is asked. An update of a tool installed system-wide puts a user-scope copy ahead of it on PATH.
• --scope user is user mode from the start; --scope system uses sudo without offering it (also where envira cannot tell that sudo is allowed, e.g. a sudoers rule for one user). The password is asked on the terminal also with -y or piped input (curl … | bash); only where there is no terminal at all (CI, cron) envira plans in user mode, unless --scope system is given.
• macOS: install Homebrew first; envira uses it for most tools and does not install it itself. Without it, only tools with another route (cargo, pipx, npm, vendor scripts) are available. Linux-only items (Docker, the default-shell and sysctl configs) show as n/a. Intel Macs are not supported yet.
• envira uses the catalog published at boot.controlnet.space/envira/catalog.toml, so new tools arrive without a new release. It is cached for an hour, and it falls back to the cache and then to the catalog built into the binary. --no-remote uses only the built-in one.
• Your own items go in ~/.config/envira/catalog.d/*.toml. envira catalog schema prints the format, and envira catalog check validates it.
• Variables for the install script: ENVIRA_VERSION=v0.2.0 pins a release, ENVIRA_INSTALL_DIR changes where it puts the binary, and ENVIRA_NO_LAUNCH=1 only installs.

The prompt that shell sets up (the mzz-ys theme):

Docker

FROM ubuntu:24.04

RUN apt-get update \
 && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends ca-certificates curl sudo zsh \
 && rm -rf /var/lib/apt/lists/* \
 && useradd -m -s /bin/zsh user \
 && echo "user ALL=(ALL) NOPASSWD: ALL" > /etc/sudoers.d/user

USER user
WORKDIR /home/user
RUN curl -fsSL https://boot.controlnet.space/envira | bash -s -- install full -y

CMD ["/bin/zsh"]

This is the setup the CI integration tests use: a normal user with passwordless sudo. For a user without sudo, drop sudo and the sudoers line and install user instead.

Legacy scripts

The shell scripts envira replaces. They still work and are still served.

curl -fsSL https://boot.controlnet.space/ | bash        # if you have sudo permission
curl -fsSL https://boot.controlnet.space/user | bash    # if you don't have sudo permission
curl -fsSL https://boot.controlnet.space/verify | bash  # verify the installation

Full tools and configurations in Docker with the legacy scripts:

FROM ubuntu:22.04

WORKDIR /root

RUN apt-get update -y
RUN DEBIAN_FRONTEND=noninteractive TZ=Etc/UTC apt-get install -o DPkg::Options::="--force-confnew" -y tzdata
RUN DEBIAN_FRONTEND=noninteractive apt-get install -y iputils-ping net-tools python3-venv apt-utils make openssh-server gedit vim git git-lfs curl wget zsh gcc make perl build-essential libfuse2 python3-pip screen fzf tmux ncdu bat pipx xsel screenfetch neofetch p7zip-full unzip tigervnc-standalone-server tigervnc-common tigervnc-xorg-extension

RUN curl -fsSL https://boot.controlnet.space/user | bash

CMD ["/bin/zsh"]

Minimal oh-my-zsh setup without extra tools:

# Setup environment
RUN sh -c "$(wget -O- https://github.com/deluan/zsh-in-docker/releases/download/v1.1.5/zsh-in-docker.sh)" -- \
    -t robbyrussell \
    -p https://github.com/zsh-users/zsh-autosuggestions \
    -p https://github.com/zsh-users/zsh-syntax-highlighting

# download theme
RUN curl -fsSL https://raw.githubusercontent.com/ControlNet/my-zsh-theme-env/main/files/mzz-ys.zsh-theme > /root/.oh-my-zsh/themes/mzz-ys.zsh-theme

# modify the .zshrc file to change the theme and add plugins
RUN cat /root/.zshrc | sed 's/ZSH_THEME=\"robbyrussell\"/ZSH_THEME=\"mzz-ys\"\nZSH_DISABLE_COMPFIX=\"true\"/' \
    | sed 's/plugins=(git)/plugins=(git zsh-autosuggestions zsh-syntax-highlighting)/' > /root/temp.zshrc
RUN mv /root/temp.zshrc /root/.zshrc

# setup git alias
RUN git config --global alias.lsd "log --graph --decorate --pretty=oneline --abbrev-commit --all"

# hide conda prefix
RUN echo "changeps1: false" >> /root/.condarc

What run.sh does, step by step:

1. Checks the Linux distribution and installs a set of common development tools using the appropriate package manager.
2. Installs pipx, a tool for installing and running Python applications in isolated environments.
3. Downloads and installs bat, a cat clone with syntax highlighting and Git integration.
4. Installs Node.js using nvm (Node Version Manager).
5. Downloads and installs ctop, a top-like interface for container metrics.
6. Installs neofetch, a command-line system information tool.
7. Sets up tmux with a specific color scheme.
8. Installs oh-my-zsh, a framework for managing Zsh configuration.
9. Changes the default shell to Zsh.
10. Downloads a specific Zsh theme and modifies the .zshrc file to use this theme and add plugins.
11. Disables oh-my-zsh auto-update notifications.
12. Installs additional Zsh plugins for autosuggestions and syntax highlighting.
13. Sets up Git history visualization and credential storage.
14. Installs Miniconda, a free minimal installer for conda.
15. Sets up the Rust programming language and Go programming language environments.
16. Installs lazygit, a simple terminal UI for git commands.
17. Installs neovim, a highly configurable text editor.
18. Sets up LunarVim, a distribution of Neovim.
19. Installs a faster solver for conda.
20. Installs the Meslo font.
21. Installs Docker and sets up the user to run Docker commands without sudo.
22. Installs lazydocker, a simple terminal UI for Docker.
23. Installs lemonade, a remote operation utility.
24. Installs ZeroTier, a global P2P VPN.
25. Installs several utilities (lsd, git-delta, duf, dust, fd, ripgrep, gping, procs, xh, uv, speedtest-cli, gdown, zoxide, micro, scc, viu, pm2) and sets up aliases for some of them.
26. Installs several system monitoring tools (bottom, nvitop, bpytop, bandwhich).

If your sudo credential times out during a long installation, run.sh refreshes sudo credentials in the background after the first sudo prompt.

License

AGPL 3.0 - see LICENSE file for details.