Hey nostr:nprofile1qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0spzcs8wumn8ghj7un9d3shjtnyv9kh2uewd9hj7qguwaehxw309ahx7um5wgknztnwvfhjuctwvasku6fwvdhj78w5jyy, when self hosting alby hub how persistent does the nwc.db (or postgres) need to be? Like if that DB happens to get deleted, but the rest of the work_dir survives, upon reboot would it just rebuild the nwc database?
In my homelab persistent storage is provided by an NFS share. Right now the entire workdir is a share. But the sqlite queries are often pretty slow (likely from the NFS overhead. Trying to decided whether I externalize a postgres DB or just let the sqlite DB write to a truly local file on the computer node (where it would lose its persistence guarantees)
Login to reply
Replies (2)
You need to have a persistent storage. Otherwise you will lose the channel's state, and then after a reboot, no channels will be found, and your channel partners will force close the channels
If you are setting up Alby Hub on a docker, or anywhere, always have persistent storage.
Thanks yea realized everything is basically in the nwc.db, I thought maybe it was just events and stuff.
Stood up a DB directly in my NAS server, then used hub's DB migration function. Everything worked great and now without the overhead of NFS things are wayyyy faster 😎