Part of it is that the blossom-compliance tool creates a temp key and if a server requires a whitelisted npub, some of the tests will fail. I submitted a PR to Kieran (npub1v0l…qj49) repo to allow an env to set an npub for testing. Other than that, just putting in the work to be spec compliant lol.
As for the peering, it's just a list of servers that don't get posted to the kind 10063 list. Each hanami instance gets assigned a random npub on first run (which makes FIPS peers possible for example), and you can set them up as backup-only (no public blob links, etc). Peers get added on each end so they communicate with each other.
Still plenty to do and document but most of it is in the readme and deployment docs already https://github.com/Letdown2491/hanami