Pxehost is much less featureful than Bootimus, no dashboard, and only supports netboot.xyz.

I am curious how Bootimus got udp broadcast to work via Docker on arm macOS. I could not figure that out and it’s why I released pxehost as a cross platform binary.

We need a good ISO to set up new hosts to run firecracker VMs in k3s. That would be a killer homelab tool. Tooling to make custom ISOs. And some Kairos/Talos immutable image update style tooling would be great too.

The dream is to boot via PXE once per host to setup secure k8s nodes, using just Ethernet cord, ISP router, and a windows laptop or an iPhone.

I do not say this to detract from the value of the project or its very interesting nature, by the way. Just an orthogonal observation.

A PXE boot server has many uses. The project already mentions using it for tools like GParted, Memtest86+ and so on. Booting live OS or OS installers via netboot.xyz is also great. But you can automate things even further; at a previous job (~18 years ago) I used PXE to serve a debian installer image with a preseed file to add user accounts with SSH keys, apt install all the dependencies, and install local binaries to get machines up and running useful stuff without needing to do any manual configuration. Nowadays you'd probably just have it do a minimal install + add just an SSH key, and then let another tool like Ansible take over the rest of the provisioning.

I run a homelab PXE & NFSboot, so no hard drives in the homelab. Works great until I do something to bork it up.

I have been fine tuning setup scripts to automatically get things going for scratch, but I always find there was one more hack I didn't automate last time.

iPXE is on my to-learn list.

That being said what may be more useful is a EFI binary you can push to a motherboard that does this with a tpm key

Slop websites are getting very old very fast.

https://vorpus.github.io/performativeUI/#/components/status-...