That’s a good idea which could easily be hacked up from the outside.
Just monitor the DHCP server for new pixelblazes, and post a .pbb (pixelblaze backup) file at it when one appears. You would probably want to change the name in the config JSON at the very least.
You could also pull the .pbb regularly, extract it to the filesystem, and track the changes in git.
So it’s possible today with some duct tape, and I could see the incoming-dhcp thing working just like a PXE system, but that’s already a bit too 1980’s for me, so writing to tftp would be a bit much. As for git, that would be neat – just configure a git server on the pixelblaze and have it pull its config by name … and presumably a tiny subset of git would fit on the ESP.
The .pbb format is a JSON file with base64 encoded files, so you could use the UI to get an archive and parse it in a tool to automate bringup for copies.
Regarding DHCP specifically, I don’t know if this would be easy to tap in to on the PB side for custom provisioning, like I’ve done with bootstrapping linux installs.
The APIs now are HTTP, fully curl-able and scriptable. Initial wifi setup could be scripted as well by scanning for new APs, connecting, and posting to the wifi config form endpoint.
I’ve definitely considered some kind of git integration. There’s a destructured format for patterns I have in mind that would make it much easier to manage via git, and having a repo backing the community patterns is on my list.