Files
esh-pfi-infrastructure/configs/homepage/services.yaml
T
vh b842212b06 fleet: register 9 hosts surfaced by gap-analysis audit
Six PFI VMs/LXCs previously known only via proxmox_inspect.sh —
covered by vzdump but not in servers/, so operational context
(roles, backup posture, ssh target) was missing:

  pfi-ana-webhost  (VMID 110)  — web workload
  ana-filebot      (LXC  112)  — file-task automation
  pfi-pteradactyl  (VMID 107)  — Pterodactyl game panel
  pfi-tacticalrmm  (VMID 111)  — TacticalRMM remote-management
  pfi-postgres     (VMID 105)  — shared Postgres (vaultwarden/gitea/
                                 paperless backends)
  ana-wg           (LXC  113)  — WireGuard VPN gateway

Plus three SureFire tenant hosts at the Anaheim colo:

  sfsrv-ana        — tenant Proxmox hypervisor (10.250.250.115:8006)
  sf-ana-container — container workload on that Proxmox
  sf-r630          — physical R630 (iDRAC 10.250.250.110 for PFI-side
                     hardware mgmt; OS is tenant-scoped)

Each server dir has README + ssh-target where applicable. SureFire
entries explicitly document tenancy scope: PFI provides hosting,
SureFire owns the OS; management actions need tenant coordination.
SureFire hosts have no ssh-target by default.

Homepage Infra - ANA gains two new cards:
  - SFsrv-ANA (https://10.250.250.115:8006, si-proxmox icon)
  - SF-R630-iDRAC (https://10.250.250.110, si-dell icon)
PFI-ANA-ML2 BMC gained an href since it has a usable web UI.

CLAUDE.md fleet table extended with all 9 new rows. Placement-rules
section notes the SureFire tenant boundary.

Memory: new project_surefire_tenant.md so future sessions know sf-*
hosts are tenant-scoped by default.
2026-04-21 14:29:43 -07:00

174 lines
5.8 KiB
YAML
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
# https://gethomepage.dev/latest/configs/services
#
# Groups are ordered by settings.yaml `layout`. This file holds the manual
# entries — infrastructure, BMCs, off-Docker endpoints, and a handful of
# well-known internal service URLs. Docker-labeled stacks auto-populate
# their own groups through the providers in docker.yaml, so most app
# entries don't need to appear here.
- Monitoring:
# Beszel, Dozzle, Backrest arrive here via Docker label auto-discovery
# (homepage.group=Monitoring on their compose files). Do not re-add them
# manually — they'll double up in the UI.
- Uptime Kuma:
href: http://10.0.50.45:3001
icon: mdi-check-network
siteMonitor: http://10.0.50.45:3001
description: Uptime monitor (esh-docker-vm)
# AI Systems group is fully Docker-auto-discovered (llama-swap, vLLM Embed,
# vLLM Rerank — homepage.group=AI Systems on their compose files). Position
# and row×3 style for the group live in settings.yaml. Do not add entries
# here or they'll double up.
- Media:
- Plex:
href: http://10.0.50.56:32400
icon: si-plex
siteMonitor: http://10.0.50.56:32400
description: Media Server (esh-nas-pve 10.0.50.56)
widget:
type: plex
url: http://10.0.50.56:32400
key: '{{HOMEPAGE_VAR_PLEX_KEY}}'
- Jellyfin:
href: http://10.0.50.57:8096
icon: si-jellyfin
siteMonitor: http://10.0.50.57:8096
description: Media Server (esh-nas-pve 10.0.50.57)
widget:
type: jellyfin
url: http://10.0.50.57:8096
key: '{{HOMEPAGE_VAR_JELLYFIN_KEY}}'
enableBlocks: true
- Games:
- Pterodactyl:
href: http://10.250.50.55/
icon: mdi-gamepad-square
siteMonitor: http://10.250.50.55
description: Game server panel
- Infra - ANA:
- ANA-Firewall:
href: https://10.250.250.1
icon: mdi-wall-fire
siteMonitor: https://10.250.250.1
description: ana-gw Fortigate 81F (ana-fw.phasefinal.com)
- PFI-r750xs-iDRAC:
href: https://10.250.250.30/
siteMonitor: https://10.250.250.30/
icon: si-dell
description: iDRAC (Dell R750xs)
- PFI-PVE:
href: https://10.250.250.31:8006/
siteMonitor: https://10.250.250.31:8006/
icon: si-proxmox
description: Proxmox hypervisor (pfi-pve)
- ANA-NAS:
href: https://10.250.50.50:9090/
siteMonitor: https://10.250.50.50:9090/
icon: mdi-nas
description: Debian NAS (Cockpit)
- ANA-FileBot:
ping: 10.250.50.53
icon: mdi-sync-circle
description: File-task VM
- PFI-VM-Docker:
href: http://10.250.50.70:5001
icon: si-docker
siteMonitor: http://10.250.50.70:5001
description: Docker VM (ana-docker, Dockge at :5001)
- PFI-ANA-ML2:
ping: 10.250.50.54
icon: mdi-brain
description: GPU host (bare-metal)
- PFI-ANA-ML2 BMC:
href: https://10.250.250.50
icon: mdi-brain
siteMonitor: https://10.250.250.50
description: BMC (ana-ml2)
- SFsrv-ANA:
href: https://10.250.250.115:8006
icon: si-proxmox
siteMonitor: https://10.250.250.115:8006
description: Proxmox (SureFire tenant hypervisor at PFI colo)
- SF-R630-iDRAC:
href: https://10.250.250.110/
icon: si-dell
siteMonitor: https://10.250.250.110/
description: Dell R630 iDRAC (SureFire tenant hardware)
- Infra - NH3:
# NH3-Firewall (Fortigate 101F at 10.100.250.1) retired 2026-04-21 —
# re-add if/when a new edge device is installed.
- NH3-SW1:
href: https://10.100.250.2
icon: mdi-switch
siteMonitor: https://10.100.250.2
description: Mikrotik CRS328-24P-4S+
- NH3-NAS:
href: https://10.100.50.50:5001
icon: mdi-nas
siteMonitor: https://10.100.50.50:5001
description: Synology RS2418+ DSM (restic target + VM storage)
- NH3-PVE:
href: https://10.100.250.60:8006/
siteMonitor: https://10.100.250.60:8006/
icon: si-proxmox
description: Proxmox hypervisor (nh3-pve)
- NH3-VM-Docker:
href: http://10.100.50.40:5001
icon: si-docker
siteMonitor: http://10.100.50.40:5001
description: Docker VM (nh3-docker, Dockge at :5001)
- NH3-Ansible:
ping: 10.100.50.42
icon: si-ansible
description: Ansible control node
- Infra - ESH:
- ESH-Firewall:
href: https://10.0.250.1
icon: mdi-wall-fire
siteMonitor: https://10.0.250.1
description: esh-gw
- Brother Printer:
href: http://10.0.90.125/
icon: mdi-printer
siteMonitor: http://10.0.90.125/
description: Brother (ESH)
- ESH-NAS:
href: https://10.0.50.50:9090
icon: mdi-nas
siteMonitor: https://10.0.50.50:9090
description: NAS share manager (Cockpit)
- ESH-PVE:
href: https://10.0.250.35:8006
siteMonitor: https://10.0.250.35:8006
icon: si-proxmox
description: Proxmox hypervisor (esh-pve)
- ESH-PVE-NAS:
href: https://10.0.50.55:8006
siteMonitor: https://10.0.50.55:8006
icon: si-proxmox
description: Proxmox hypervisor (esh-pve-nas, storage/media)
- ESH-FileBot:
ping: 10.0.50.70
icon: mdi-sync-circle
description: Restic / file-sync VM (esh-nas-pve) — role TBC
- ESH-VM-Docker:
href: http://10.0.50.45:5001
icon: si-docker
siteMonitor: http://10.0.50.45:5001
description: Docker VM (esh-docker-vm, Dockge at :5001)
# Service Networking group is now fully Docker-auto-discovered (Traefik ×2,
# AdGuard ×2, Dockge ×5, rest-server-ana, mailrise, etc. all carry
# homepage.group=Service Networking on their compose files). Position and
# layout live in settings.yaml. Do not add entries here or they'll double up.
#
# Mosquitto (ESH) note: still labeled Apps on its compose; once moved to
# Service Networking via a label change on esh-docker-vm, it auto-populates.