nathan
016d38d5ab
- Add service management prompts (review, standardize, troubleshoot, integration) - Add Docker Swarm migration and tutoring workflows (swarm-migration, swarm-tutor) - Add SSO onboarding guide for Authentik integration (sso-onboarding) - Add session lifecycle prompts (start, end, status) for context continuity - Add node bootstrap scripts for Debian Trixie (day0bootstrap.sh) and Ubuntu/Debian (pi_init.sh) These prompts implement gated, step-by-step workflows with explicit confirmation requirements to prevent accidental changes during service operations. Bootstrap scripts standardize IP configuration (10.0.0.200) and install Docker + Ansible on new nodes.
scripts
Automation utilities and helper scripts for homelab infrastructure management.
Inventory
| Script | Purpose | Status |
|---|---|---|
| onboarding.sh | Bootstrap Ansible control node for Proxmox management | 🟡 DRAFT - Testing Required |
onboarding.sh
Purpose: Automated setup of Ansible control node for Proxmox infrastructure management.
What it does:
- Installs Ansible and Proxmoxer Python library
- Detects or generates SSH keypair (ED25519 preferred, RSA fallback)
- Copies public key to Proxmox server for passwordless authentication
- Generates Ansible inventory file (
hosts.ini) with Proxmox connection details
Prerequisites:
- Debian/Ubuntu-based system (uses
apt) - Network access to Proxmox server
- Initial SSH password for target Proxmox server
Configuration: Edit the following variables at the top of the script:
PROXMOX_IP="192.168.1.100" # Target Proxmox server IP
PROXMOX_USER="root" # Proxmox SSH user
Usage:
cd ~/dev/homelab/scripts
chmod +x onboarding.sh
./onboarding.sh
Verification:
ansible proxmox_nodes -m ping -i hosts.ini
⚠️ Development Status
| Script | Testing Status | Known Issues |
|---|---|---|
| onboarding.sh | ❌ Untested in production | • Hardcoded Proxmox IP/user variables • No error handling for failed SSH key copy • Assumes Debian/Ubuntu package manager • No validation of Proxmox connectivity |
DO NOT USE IN PRODUCTION until the following are addressed:
- Error Handling: Add validation checks for each step
- Idempotency: Verify script can be safely re-run
- Multi-OS Support: Test on RHEL/Arch variants or add OS detection
- Interactive Mode: Prompt for PROXMOX_IP/USER instead of manual editing
- Rollback: Add cleanup mechanism for failed installations
Contributing
When adding new scripts:
- Update the Inventory table with script name and purpose
- Document prerequisites, configuration, and usage
- Mark status as 🟡 DRAFT until production-tested
- Add to Development Status table with known issues