it can be configured when self hosting through an env variable
Sadly, it doesn't look like nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qyw8wumn8ghj7mn0wd68ytf39ehxymewv9hxwctwdyhxxme0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshszymhwden5te0wp6hyurvv4cxzeewv4ej7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uq3jamnwvaz7tmjv4kxz7fwwdhx7un59eek7cmfv9kz7qpqgetal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqygds4v included a way to customize what relay Alby Hub uses for NWC connections, unless I am completely missing it somewhere.
Discussion
Any chance of putting it in as an advanced option in the UI in the future?
that’s currently not planned, because the architecture currently requires it to be set at startup.
Got it. So ssh into my Start9, open the .env config, and I should find a variable there for what relay to talk to for NWC. Edit it, save and exit, then restart Alby Hub and update all of my NWC connections to use that relay? The rest of the connection string should stay the same, right?
yes, check the readme:
also any existing connections will break (as the relay changes) so you have to configure the apps connections again.