Files
Provisioning/deploy/provisioning.example.yaml
josh b23ef64ee1
build-and-push / test (push) Successful in 9m57s
build-and-push / build-and-push (push) Has been cancelled
Use ephemeral SSH keys per rebuild instead of static config keys
Generate a fresh ed25519 key pair at rebuild time, inject the public key
into the Proxmox answer file, use the private key for cluster join over
SSH, then remove the key from both the remote host and the database.
This eliminates the need to manage static SSH keys in config/secrets.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-05-03 21:09:22 -04:00

39 lines
815 B
YAML

server:
bind: "0.0.0.0:8080"
public_url: "http://192.168.1.100:8080"
database:
path: "/data/provisioning.db"
pxe:
enabled: true
interface: "eth0"
subnet: "192.168.1.0/24"
runtime_dir: "/data/pxe"
tftp_root: "/data/tftp"
dnsmasq_bin: "/usr/sbin/dnsmasq"
images:
dir: "/data/images"
proxmox:
existing_node: "192.168.1.10"
cluster_name: "homelab"
join_fingerprint: "AA:BB:CC:DD:EE:FF:00:11:22:33:44:55:66:77:88:99:AA:BB:CC:DD:EE:FF:00:11:22:33:44:55:66:77:88:99"
credentials:
root_password_hash: "$6$rounds=5000$randomsalt$hashedpasswordhere"
infrastructure:
base_url: "http://192.168.1.50:3000"
room_id: 1
server_type_map:
minisforum-ms-01: 1
minisforum-um790: 2
timeout_seconds: 10
locks:
ttl_minutes: 60
server_types_path: "/etc/provisioning/server-types.yaml"