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

S3 source support #4506

Open
lynncyrin opened this Issue May 3, 2016 · 4 comments

Comments

Projects
None yet
5 participants
@lynncyrin
Member

lynncyrin commented May 3, 2016

From: bundler/bundler-features#46

The plugin system is mentioned in that issue, which is likely once next feature release the changes 1.12 are stable. Issues for the plugin system are here https://github.com/bundler/bundler/issues?utf8=%E2%9C%93&q=milestone%3A%221.X+--+Plugin+System%22

@segiddins

This comment has been minimized.

Show comment
Hide comment
@segiddins

segiddins Aug 8, 2016

Member

I think @asutoshpalai has been working on this as a plugin?

Member

segiddins commented Aug 8, 2016

I think @asutoshpalai has been working on this as a plugin?

@tmaier

This comment has been minimized.

Show comment
Hide comment
@tmaier

tmaier Dec 25, 2016

+1 on this. I prepared a Dockerfile and some shell scripts which upload the gems to s3 and create the index. https://github.com/tmaier/docker-s3-gemserver

The only thing missing for the perfect solution is native s3 source support in Bundler. As far as I know rubygems supports already s3. rubygems/rubygems#856

What is requried from solution architecture perspective to get Bundler working with S3? Would it simply utilize rubygems' S3 capability?

tmaier commented Dec 25, 2016

+1 on this. I prepared a Dockerfile and some shell scripts which upload the gems to s3 and create the index. https://github.com/tmaier/docker-s3-gemserver

The only thing missing for the perfect solution is native s3 source support in Bundler. As far as I know rubygems supports already s3. rubygems/rubygems#856

What is requried from solution architecture perspective to get Bundler working with S3? Would it simply utilize rubygems' S3 capability?

@devoptimist

This comment has been minimized.

Show comment
Hide comment
@devoptimist

devoptimist Mar 13, 2018

+1 for this. I am wondering if anyone is working on this, or if there is any context around why it has not been implemented yet. it would be a really useful feature to have

devoptimist commented Mar 13, 2018

+1 for this. I am wondering if anyone is working on this, or if there is any context around why it has not been implemented yet. it would be a really useful feature to have

@jfharden

This comment has been minimized.

Show comment
Hide comment
@jfharden

jfharden May 23, 2018

Also +1 for this, it would allow much finer grained access controls, current private repo options are a bit limited and being able to provide access via IAM permissions would be wonderful 👍

jfharden commented May 23, 2018

Also +1 for this, it would allow much finer grained access controls, current private repo options are a bit limited and being able to provide access via IAM permissions would be wonderful 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment