Skip to content
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

move away from AWS for storage #56

Open
mcfiredrill opened this issue Dec 15, 2020 · 3 comments
Open

move away from AWS for storage #56

mcfiredrill opened this issue Dec 15, 2020 · 3 comments
Assignees

Comments

@mcfiredrill
Copy link
Member

https://www.digitalocean.com/community/tutorials/how-to-migrate-from-amazon-s3-to-digitalocean-spaces-with-rclone

@mcfiredrill
Copy link
Member Author

Should be able to use the same Gem even.
https://www.digitalocean.com/docs/spaces/resources/s3-sdk-examples/

@dudethatbe
Copy link
Contributor

Other than the S3 tokens, I think I need you to try creating a token for the Digital Ocean Space https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key#creating-an-access-key. Whenever I try to manage the keys for the streampusher space you've already created, it redirects to my personal tokens and doesn't seem to allow me to look the configuration of the space itself

@mcfiredrill
Copy link
Member Author

Backblaze might be a decent option as well, its what resonate uses for storage I believe.
https://www.backblaze.com/

@mcfiredrill mcfiredrill changed the title migrate to DO spaces for storage move away from AWS for storage Apr 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants