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

implement an S3 backend #26

Open
clux opened this issue Nov 28, 2017 · 1 comment
Open

implement an S3 backend #26

clux opened this issue Nov 28, 2017 · 1 comment

Comments

@clux
Copy link
Member

clux commented Nov 28, 2017

No description provided.

@bencord0
Copy link
Member

bencord0 commented Jun 3, 2018

For local development, or for users who don't wish to use S3, we could use minio.

I think, that for projects in the open, it should be possible to fetch artifacts from a public S3 bucket, but gracefully deny publishing unless the user has the necessary access tokens to write to the S3 bucket.

For projects that don't want to have public artifacts, we should permit them to use arbitrary, S3 compatible, endpoints. With minio, this could be on a local laptop, but there are many other S3 implementations out there (I'm also a fan of OpenStack Swift for this purpose).

Minio is also available on the Docker Hub.

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