Is this gem still maintained?

[erdostom]

I see several forks and the official version is still not on Litestram v0.5

Seeing how sqlite databases are becoming the norm even in production for many Rails apps, it would be great to have have an up to date backup solution.

If there's no interest (or time or energy) in maintaining the gem here, maybe a fork can take over?

[fractaledmind]

I have fallen off, true enough. If anyone wants to help me keep releases in sync with upstream, I'm happy to get some support. I'll work on an update this weekend

[cole-robertson]

Happy to help with this as well. I've opened three PRs:

• Run Litestream commands without a shell and surface failures #76 — commands run without a shell and raise on failure (today a failing
  command returns "" and looks like success)
• Give the Puma plugin the pid of the litestream process #77 — the Puma plugin holds the real litestream pid, so stopping Puma stops
  replication
• Update to Litestream 0.5.17 #78 — binary to 0.5.17: checksums, ltx/status, 0.5 config shape. Depends
  on Run Litestream commands without a shell and surface failures #76.

The first two are bugs on 0.3.13, so they stand alone. Otherwise, this is an attempt as a path to least friction to get us up-to-date with upstream v0.5+.

#78 keeps the dashboard on the CLI so it still works when replicate runs in its
own container. @alxvernier's #73 composes on top of that as an enrichment, and
I'd rather see it land. After, we can take a closer look at the IPC story with different deployment options.

At Rebulk, we run 0.5.17 in production with our fork, so I'm glad to open the bump PR on each upstream
release: version, checksums, command changes and keep an eye open here.