Error: A Tigris project named my-app-bucket-1 already exists for app my-app
If I can’t have two buckets in the same Fly app, then would there be any problems/conflict with connecting both TigrisFS (for non-database files) and Litestream (for a SQLite database that’s at a different local path than the one mounted to TigrisFS) to the same bucket? Would they automatically use differently named objects within the bucket and stay out of each other’s way?
I’m still learning about Litestream, and looks like it supports different replica types, not just s3. So, for example, one possibility might be to replicate to a local path that’s within the TigrisFS mount, thereby ensuring that only the TigrisFS process is the one communicating with the Tigris bucket.
TigrisFS mainly makes the Tigris bucket available as a local mount on your machine. It wouldn’t interfere in any way. Of course, if you modify the files in the directory that Litestream is configured to use, then that would be a problem. So make sure litestream is configured at a different path s3://BUCKETNAME/PATHNAME and the path within the bucket that you will use for non-database files are different.