Self-hosted Alby Hub has a RELAY environment variable that can be set to specify the relay used for NWC. I’ve built a strfry relay on a cheap VPS which I am using with my Alby Hub so I can now send NWC zaps without reliance on Alby’s relay. Seems to work well.
I’m not sure if I will keep this set up but after the issues with Alby a few days ago I wanted to confirm this works. There is still the reliance on Alby for the lightning address to receive zaps though.
How do you change this variable?
Also, I cannot zap you
I wonder if I somehow broke incoming zaps while experimenting..
Must have, I use LNbits for incoming zaps. To mitigate this issue with Alby
Seems like the Alby lightning address may also rely on the relay in some way. Will have to try to figure out what is going on and if it is possible to still use their lightning address without their relay..
Your work on this is crucial! Thank you for spearheading the effort!
Hey friend. Take a look at https://git.devvul.com/asara/well-goknown
The code in the alby dir should be enough to get a lnaddr setup with albyhub without having to make an alby account.
I don't think my zap receipts work yet but they might.
Other than that it should allow you to set up multiple lightning addresses backed by various wallets in alby.
Let me know if it works for ya!
I’m running it using Docker Compose so it was just adding the RELAY= to the environment section of the docker-compose file.
Ah! That would make things simpler.
I am running on start9 and really wanting to create a video showing others how to change this. However it’s still using v1.13.0 and much more complex to change variables on the start9 OS.
I was initially going to try start9 when I was building my new node but had issues getting it to work on the hardware I was using so ended up building everything manually on Linux. It was more work but in the end I’m glad I did it that way.
