Proxmox VE, and a foundation for community connectors
Proxmox VE
Point Homedex at a Proxmox node or cluster and every node, VM and LXC container lands in the inventory: which node each guest runs on, whether it is running, stopped or paused, and the IP addresses running guests report. Routes that point at a guest's IP now resolve to the service behind them.
- Read-only API token. Create a privilege-separated token with the PVEAuditor role. Homedex only lists nodes and guests and asks running guests for their addresses; it never reads guest configs, consoles or anything else.
- Self-signed certificates handled properly. Press Test connection with the certificate field empty, compare the fingerprint it shows with the one under the node's System > Certificates, and paste it to pin it. Or paste the cluster CA from
/etc/pve/pve-root-ca.pem, which survives certificate renewals. - One machine, many views. A Proxmox guest that is also a Tailscale device, and also known by a local DNS name, links to the one machine your Docker or SSH source reports, so its routes resolve whichever name they use. When two guests claim the same machine, Homedex leaves them unlinked rather than guess.
- Guest power state is tracked, so a VM that stops or starts shows up in the change feed.
Try it in the live demo, which now includes a Proxmox node with two guests.
Groundwork for Unraid, TrueNAS, Pi-hole, AdGuard Home and Kubernetes
These connectors are open as good first issues (#7 to #11). This release lands the shared pieces they need, so each one is now just a connector package:
- the new host kinds (
unraid,truenas,dns,k8s-node); - DNS views, so a route to
nas.home.arparesolves to the machine at that name's address; PostJSONandPostForm, bounded helpers for logins and GraphQL that never resend a credential to another host or in the clear.
Also in this release
- Connectors never follow a redirect to another host with credentials attached, and a POST that carries a password follows only a same-host upgrade to HTTPS.
Upgrading
Migrations 0010 and 0011 run on first start: 0010 adds a column and 0011 rebuilds the hosts table in place, keeping every id, note and history entry. Take a backup first as usual; see the upgrade and backup notes.
The one-file install now follows the 0.2 line. If you installed with the downloaded docker-compose.yml, download it again (or set HOMEDEX_VERSION=0.2), then run docker compose pull and docker compose up -d.
Container images are published to ghcr.io/harshshah0203/homedex.