-
Notifications
You must be signed in to change notification settings - Fork 676
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
Any plan for DigitalOcean Spaces support? #898
Comments
No, we don't have plans to support something new. |
👋 It's worth noting that DigitalOcean Spaces is S3 compatible. So you can actually use it with Backups already as you can pass configuration directly through to fog_options. Besides adjusting the endpoint, I've found that forcing usage of v2 signature type is also needed. Here's the config I'm using: store_with S3 do |s3|
s3.access_key_id = "MYKEY"
s3.secret_access_key = "MYSECRET"
s3.region = "nyc3"
s3.bucket = "log-space"
s3.path = "/"
s3.keep = 3
s3.fog_options = {
:endpoint => 'https://nyc3.digitaloceanspaces.com",
:aws_signature_version: 2
}
end |
Agreed, DO spaces works with the s3 adapter. Plus I don't think we're actively adding new storage options. |
@andrewsomething - Thanks for that. I would be very happy to take a documentation patch to cover this: the docs Website is a standard Jekyll/GitHub Pages thing on the gh-pages branch. |
https://developers.digitalocean.com/documentation/spaces/#introduction
The text was updated successfully, but these errors were encountered: