I'm working on standing up a PDS with pds-gatekeeper, which hardens the admin endpoints pds-operator needs to work. Since I'm planning to stand up both the PDS and the Operator on Fly.io, I can bypass this restriction by having Operator access the PDS's admin endpoints over the private internal network. This keeps the admin endpoints locked down and allows Operator to do its magic.
The issue is that the project currently hardcodes https and wss URLs, but internal private networks typically operate over plain HTTP with no SSL. This is generally fine, because those routes aren't exposed to the public internet.
What I've done is add a PDS_ADMIN_URL env var. This URL supports origin just like PDS_HOSTNAME does, but it also supports protocol and port. This enables the specific scenario I'm setting up: accessing otherwise blocked admin endpoints over an internal private network.
I feel like it would make sense to make PDS_HOSTNAME more configurable as well, but I wasn't sure about release cycles or stability for other projects so I didn't wanna risk borking other people's setups by futzing with it. 😅