Can I share a LiteFS SQLite DB across separate apps?

[gcv]

@scatterinfo

Is it possible to point both my production and staging apps at the same database file, so they reuse the same data? I know LiteFS can be distributed within the same app by scaling up a primary instance to multiple replicas. My question is based on entirely different apps (potentially created on different Fly accounts). Another use-case might be I want to use production data in my local environment.

Here you have the answer to your question.

Multiple apps using the same SQLite databases

Yes, it’s possible to share a LiteFS cluster across apps as long as they’re in the same organization. You’ll just need to have the same FLY_CONSUL_URL set if you’re using Consul-based leasing and you’ll need to use the same lease key: lease: type: "consul" consul: key: "mykey" It’s probably easiest to have your candidate nodes in the same app & region but LiteFS will work across any group of machines.

@scatterinfo

With Postgres or Mongo I would just reuse the same connection string or database URL on each app. What is the equivalent here?

If you want to do the same as you do with Postgres or Mongo, and solve the different Fly accounts issue, you can use Query (I’m the author).

Query is a Rust server for your remote SQLite databases and a CLI to manage them.

To set up a staging environment, you can create a branch from a production database and work with it. Essentially, a branch is a copy of the database that allows you to use the same data as in the production database and make modifications to it without affecting your production environment. This ensures that any changes you make can be safely tested and refined before being implemented in the live environment.

Another benefit of Query is that you can use Query Studio to explore and manipulate your remote SQLite databases.

I apologize for the auto-promotion