Looks like the code is here: https://github.com/benbjohnson/litestream/tree/v0.5 https://github.com/benbjohnson/litestream/tree/v0.5 Really nice to see this, I

Looks like the code is here: https://github.com/benbjohnson/litestream/tree/v0.5 https://github.com/benbjohnson/litestream/tree/v0.5 Really nice to see this, I wrote this comment almost 2 years ago when I was a little miffed about trying to use litestream and litefs: https://news.ycombinator.com/item?id=37614193 https://news.ycombinator.com/item?id=37614193 I think this solves most of the issues? You can now freely run litestream on your DB and not worry about issues with multiple writers? I wonder how the handoff is handled. The read replica FUSE layer sounds like a real nice thing to have. edit: Ah, it works like this: https://github.com/benbjohnson/litestream/pull/617 https://github.com/benbjohnson/litestream/pull/617 > When another Litestream process starts up and sees an existing lease, it will continually retry the lease acquisition every second until it succeeds. This low retry interval allows for rolling restarts to come online quickly. Sounds workable!