allbctl

allbctl

allbctl is short for allbrightctl and represents a command line interface for computer operations that I (Andrew Allbright) do. This is meant to be a CLI that is used by myself.

Docs

# Help
allbctl --help

# System status (like neofetch, but better!)
allbctl status                     # Shows comprehensive system information:
allbctl cs status                  # Same as above (alias)
                                   # - User@hostname header with separator
                                   # - OS, kernel, uptime, host/virtualization info
                                   # - Package counts (dpkg, rpm, flatpak, snap, brew, etc.)
                                   # - Shell, terminal, CPU, GPU(s), memory
                                   # - Computer setup status (dotfiles, directories, tools)

# List installed packages
allbctl list-packages              # Summary: just show counts per package manager (default)
allbctl list-packages --detail     # Full listing of all packages
allbctl list-packages -d           # Short version of --detail
allbctl list-packages apt          # List only apt packages (shows command for copy/paste)
allbctl list-packages npm          # List only npm packages (shows command for copy/paste)
allbctl list-packages flatpak      # List only flatpak packages (shows command for copy/paste)

# Computer setup (bootstrap development environment)
allbctl computer-setup status      # Check what's set up and what's missing
allbctl computer-setup install     # Install/configure dev environment automatically
allbctl cs status                  # Short alias for status
allbctl cs install                 # Short alias for install

# What computer-setup does:
# ✅ Ensures ~/src directory exists
# ✅ **Automatically installs git** (cross-platform: apt/dnf/yum/pacman/zypper/apk on Linux, brew on macOS, winget/choco/scoop on Windows)
# ✅ **Automatically installs GitHub CLI (gh)** (cross-platform package manager support)
# ✅ **Generates SSH keys** (if missing) and **registers them with GitHub** automatically
# ✅ **Clones dotfiles** from https://github.com/aallbrig/dotfiles to ~/src/dotfiles
# ✅ Runs dotfiles install script (./fresh.sh) which sets up:
#    - oh-my-zsh
#    - Symlinks for .zshrc, .gitconfig, .vimrc, .tmux.conf, .ssh/config
#    - zsh as default shell (on Linux)
# ✅ Checks tools referenced in shell config files (.zshrc, .bashrc, etc.)
#    - Detects commands in $(command), source <(command), which/command -v, eval patterns
#    - Shows which tools are INSTALLED (green) vs MISSING (red)
#    - Groups by config file with $HOME path notation
# ✅ **Fully cross-platform** - Works on Linux, macOS, and Windows
# ✅ **Idempotent** - Safe to run multiple times, only installs what's missing

Features

System Status

The status and cs status commands provide a neofetch-inspired view of your system:

• User@Hostname Header: Shows current user and machine name with separator line
• OS Information: Platform, version, architecture, kernel version
• System Details: Host/virtualization info, uptime
• Package Counts: Inline display of packages from detected package managers (dpkg, rpm, pacman, snap, flatpak, brew, choco, winget)
• System Info: Shell, terminal, CPU with core count and frequency, GPU(s), memory usage
• Computer Setup Status: Dotfiles location, required directories, installed tools, SSH configuration

Package Management

Multi-platform package detection supporting:

• Linux: dpkg, rpm, apt, dnf, yum, pacman, snap, flatpak, zypper, apk, nix, homebrew
• macOS: homebrew, macports, nix
• Windows: chocolatey, winget, scoop, plus WSL package managers
• Runtime: npm, pip, gem, cargo, composer, maven, gradle, go (all platforms)

Supported Package Managers

Usage:

• allbctl list-packages - Summary of all detected package managers
• allbctl list-packages <manager> - List packages for a specific manager (e.g., apt, npm, flatpak)
  • Displays the underlying command for easy copy/paste (e.g., "Command: apt-mark showmanual")
• allbctl list-packages --detail - Full listing of all packages from all managers

Computer Setup Automation

Fully automate bootstrapping a new development machine with dotfiles and essential tools.

Features:

• Cross-platform tool installation: Automatically installs git and GitHub CLI using native package managers
  • Linux: apt, dnf, yum, pacman, zypper, apk
  • macOS: Homebrew
  • Windows: winget, chocolatey, scoop
• SSH key management: Generates SSH keys if missing and automatically registers them with GitHub
• Creates required directories (~/src, ~/bin)
• Dotfiles integration: Clones your dotfiles repo to ~/src/dotfiles and runs install script
• Shell Config Tool Detection: Automatically scans your shell configuration files (.zshrc, .bashrc, .bash_profile, .profile) to find tool dependencies
  • Extracts commands from: $(command), `command`, source <(command), which command, command -v, eval "$(command)"
  • Reports which tools are INSTALLED (green) vs MISSING (red)
  • Groups output by config file with $HOME paths for portability
  • Filters out common shell builtins to focus on external tools
  • OS-agnostic: works on Linux, macOS, and Windows
• Idempotent operations: Safe to run multiple times, only installs what's missing

Bootstrapping a New Machine

On a fresh machine (Linux, macOS, or Windows), you can bootstrap your dev environment:

# 1. Download the latest release from GitHub
# Visit https://github.com/aallbrig/allbctl/releases/latest
# Download the appropriate binary for your platform:
#   - allbctl-linux-amd64 for Linux
#   - allbctl-darwin-amd64 for macOS (Intel)
#   - allbctl-darwin-arm64 for macOS (Apple Silicon)
#   - allbctl-windows-amd64.exe for Windows
# Make it executable (Linux/macOS): chmod +x allbctl-*
# Move to your PATH (e.g., ~/bin or /usr/local/bin)

# 2. Check your system status
allbctl status

# 3. Check what needs to be set up
allbctl cs status

# 4. Run the automated setup
allbctl cs install

# The tool will automatically:
# - Install git if not present (using your system's package manager)
# - Install GitHub CLI if not present
# - Generate SSH keys if missing
# - Register your SSH keys with GitHub (requires 'gh auth login' first)
# - Create ~/src directory if needed
# - Clone your dotfiles repo to ~/src/dotfiles
# - Run the dotfiles install script (./fresh.sh)
# - All operations are idempotent - safe to run multiple times

Contributing

Please reference the CONTRIBUTING.md file.