ActionPak

What it sets up

One script, a spread of the tools a homelab actually runs on, grouped by what they do:

The menu

Run the script and this is what you get. Pick a number, and that tool installs and configures itself. No manual command-line setup for any of them.

Run it

The script checks for its own prerequisites, pulls itself down, makes itself executable, and launches the menu. Copy the whole block into your terminal.

# Check and install sudo if not present
if ! command -v sudo &> /dev/null; then
    apt-get update && apt-get install -y sudo
fi

# Check and install curl if not present
if ! command -v curl &> /dev/null; then
    sudo apt-get update && sudo apt-get install -y curl
fi

# Download the script
sudo curl -s https://raw.githubusercontent.com/Baslocal/Homelab/main/actionpak.sh > actionpak.sh

# Make the script executable
sudo chmod +x actionpak.sh

# Run the script
sudo ./actionpak.sh

Why I built it

Every one of these tools has its own setup, its own quirks, its own way of failing on a fresh box. I'd done each of them by hand enough times that the steps were muscle memory, so I put that muscle memory into a script. The goal was accessibility: someone new to homelabs should be able to stand up real infrastructure without needing to already know how. It works the same for someone experienced who just doesn't want to type it all again.