LiteFS Cloud is being sunset next month

[MoSattler]

Fly io is sunsetting LiteFS Cloud:

We’ve decided to wind it down. LiteFS Cloud will continue to be available until October 15, 2024. - Fly.io blog

This might require some updates in the readme, like here:

LiteFS Cloud is a service offered by Fly.io for managing backup and restore functionality. - Epic-Stack Database Docs

[kentcdodds]

Thanks for opening this. I need to evaluate the options and decide which to go with. Got tied up with the Epic React v2 launch. Hopefully I'll have an answer (and maybe migration guide) for what's next before the sunset date.

I'm definitely open to suggestions, especially from folks who have tried alternatives and liked them.

[MoSattler]

@benbjohnson made some recommendations:

Disaster Recovery Without LiteFS Cloud

There are two good options.

LiteFS + Litestream

You can use Litestream to maintain your own backups to an S3-compatible object storage such as Tigris. That’s what we do internally. If you’re running a static primary, you can point Litestream at your primary node in your cluster.

Turso

If you’re interested in running a fully-managed SQLite service, we like Turso. You can find more information on their Quick Start page.

[buildtheui]

Hi everyone, I wanted to share my experience migrating to static leasing with Litestream and Tigris. Although I'm not using the Epic Stack, I was heavily inspired by it to build my backend in Golang using LiteFS and LiteFS Cloud. Since the concepts are similar, I thought it would be helpful to share my progress.

I followed the short migration guide from Fly.io and encountered a few challenges along the way. I’ve documented the issues here. However, I’ve hit a roadblock: I can't figure out how to set the lease.hostname to the primary machine ID for all nodes (both primary and replicas).

I’m not a Fly.io expert, so if anyone has a better approach or suggestions, this would help everyone.

[buildtheui]

As another option, @stephen built a drop-in solution for Litefs cloud, more details here

[stephen]

👋 litefs-backup is a stripped down fork of the original LiteFS Cloud implementation, so you're self-hosting your backup solution.

My primary motivation was to continue to have support for LiteFS' dynamic/consul leasing.

[MoSattler]

Looks like so far LiteFS Cloud is still available 🤔

[MrSucik]

some functionalities are shut down already

[MoSattler]

Ah really? which ones?

[timothymalcham]

Just checking to see if anyone has used litefs-backup or another solution successfully with the Epic Stack? Did it work as a drop-in replacement, any issues? I've got a couple client projects built with the Epic Stack and would like to implement something automated for backups.

[MoSattler]

I have bitten the bullet and migrated to Postgres :(