Files
bootstrap/readme.md
2026-06-20 17:57:05 +05:30

4.9 KiB

Bootstrap

A collection of bootstrap scripts for setting up tools and configurations I use across new machines, servers, and development environments.

The goal is simple: reduce the number of manual steps required after installing an operating system and make my setup reproducible.

Available Scripts

Bootstrap is designed to be completely environment-agnostic and self-contained. Each bootstrap script automatically detects your platform (supporting Arch Linux, Debian/Ubuntu, Fedora, etc.) and architecture, installs the necessary dependencies using the native package manager or verified binary downloads, and cleanly configures your shell environment. This removes the overhead of maintaining multi-platform scripts and eliminates the need to run raw, complex pipelines from the web.

Here is a comparison of the size and complexity of using Bootstrap (to b) versus running the original, official installation scripts (not to b):

application to b not to b
Antigravity CLI (agy) 197 lines 239 lines (Official Antigravity install script)
Bat (bat) 155 lines N/A (Standard package install)
Node.js & NVM (node) 156 lines 507 lines (Official NVM install script)
Neovim (nvim) 178 lines N/A (Official binary/config distribution)
PNPM (pnpm) 245 lines 213 lines (Official get.pnpm.io script)
Rust (rust) 155 lines 921 lines (Official sh.rustup.rs script)
Starship (starship) 132 lines 554 lines (Official starship.rs script)
Yay (yay) 96 lines N/A (Official manual build process)
Yazi (yazi) 163 lines N/A (Standard package install)
Zoxide (zoxide) 90 lines 466 lines (Official zoxide install script)

More scripts will be added over time.

Usage

To bootstrap a new machine and set up the b command tool, run the following:

curl -fsSL https://adityagupta.dev/b | bash

Once bootstrapped, you can run any installer script using the b command followed by its shortcut name. You can also chain multiple installations by separating their names with a comma:

b nvim
b yazi
b nvim,yazi

You can also edit configurations located in your ~/.config/ directory by running:

b con nvim
b con i3

It automatically fuzzy-finds the folder in case there is no exact match.

To check for updates and update the tool manually:

b up
# Or to force a reinstall of the CLI files:
b up --force

Uninstallation

To completely remove the bootstrap helper tool and clear out the shell configurations (leaving any installed software configs intact), run:

b bye

Then reload your shell configuration or run unset -f b to clear the function definition from your current terminal session.

Development

If you are developing this tool locally:

  1. Clone the repository.
  2. Run ./bootstrap.sh to install the CLI from your local copy. This will also automatically install a Git pre-commit hook (scripts/pre-commit) that auto-increments the patch version in the VERSION file on each commit.

Philosophy

These scripts are designed for my own systems first.

That means they may make assumptions about:

  • Preferred software choices
  • Directory layouts
  • Configuration locations
  • Existing infrastructure

The scripts are intentionally straightforward Bash scripts that can be inspected and modified before execution.

Future Plans

Potential additions include:

  • Development environment bootstrap
  • Workstation setup
  • Server provisioning
  • Dotfile installation
  • Container and virtualization tooling
  • Personal utilities

Security

Running scripts directly from the internet is convenient but should always be approached with caution.

Why Bootstrap is More Secure

Instead of blindly piping large, third-party installation scripts (often hundreds or thousands of lines of unscrutinized code) directly from the internet into your shell, Bootstrap uses a scrutinized and simplified approach:

  1. Audited & Minimised: Every script in installers/ has been scrutinized, refactored, and stripped of redundant compatibility layers (like Windows/macOS support or complex environment checks), leaving only the essential, readable logic required for your setup.
  2. Controlled Execution: Since installer scripts are hosted locally in your cloned repository, you can review every line of code before executing it. You are never subject to silent, upstream changes to installers.
  3. No Raw Pipes: We download official binary releases directly to verified temporary locations rather than running arbitrary third-party script pipelines.

If you want to audit the core Bootstrap CLI itself before running it:

curl -fsSL https://git.adityagupta.dev/sortedcord/bootstrap/raw/branch/master/bootstrap.sh
curl -fsSL https://git.adityagupta.dev/sortedcord/bootstrap/raw/branch/master/routes.sh

and review the contents before piping it into a shell.

License

MIT