-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Limited support for S3-compatible storage #491
Comments
I also use Storj and reach the same problem |
+1 for this |
I have litestream working with Oracle Cloud S3-compatible storage. The key is to use https endpoint, like this in my config:
Try doing the same with Storj. |
The issue is valid, though, as there shouldn't be an allow/deny list for third party providers but instead just allow the user to configure forcePathStyle in all cases. The https endpoint trick is what seems to be best workaround for now. |
On IDrive e2 S3-compatible storage, this works for me. (No https:// nor s3:// in endpoint.)
litestream v0.3.13 |
Anyone googling for Cloudflare R2 Storage for Litestream may run into the issue I kept having, where it seems to require a region to be happy. R2 has documentation on this, and effectively says just use My configs that are working as of today, 2024-02-02:
Hope this helps the lost googler! |
Hello @benbjohnson, first of all, thank you for your fantastic work on this project.
I am working with S3-compatible storage called Storj. I have tried to restore a replica.
Litestream config:
Litestream restore:
I think the following lines may contribute to the problem.
litestream/cmd/litestream/main.go
Lines 457 to 480 in 749bc0d
litestream/s3/replica_client.go
Lines 696 to 738 in 749bc0d
AFAIK,
forcePathStyle
should be true for non-AWS S3 storage. However, the above function will overwriteforcePathStyle
for any other S3-compatible service that is not Localhost, Backblazeb2, Filebase, Digital Ocean or Linode.The text was updated successfully, but these errors were encountered: