-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
bundler: how can i make --full-index
automatic?
#3806
Comments
@ljharb We would welcome a PR to add a config option if this is something you would like to see in Bundler. Here's an example PR rubygems/bundler#6309 |
@colby-swandale thanks - that example PR tho references files and terms that no longer exist, like |
Also, any tips on where would be the best place to read/respect the config value? I was thinking either the CLI (as a |
Sorry for chiming in this late. I'd like to ask some more background for this because for a long time I haven't heard of anyone using this option. When I started contributing to |
@deivid-rodriguez my company's internal |
Hi @ljharb. Yeah, I understand the request 👍. My concern is that the new API (what's used by default without the As a matter of fact, we have recently started considering stopping using the old API at all in So I feel adding a configuration to always use |
We haven't received any further feedback, so I'll close this for the moment. I still would like to figure out what's going on here, so feel free to reopen this and post more information so we can try figure this out! |
@deivid-rodriguez unfortunately i'm unable to share it, but i have a long gist of log output. Since we're using a gem bucket from S3, i don't think we can take advantage of any new APIs :-/ |
Could you at least share the gist, with any "private stuff" masked or removed or something? So... You're using a private gem source using gemstash? I think that would make sense since, it seems it doesn't yet support the new Compact Index API. So, that being the case, using Does this make any sense @bronzdoc? |
If I'm right, we should move this ticket to |
@ljharb Can you confirm whether you're using a private gem source through gemstash? I think you should see those 403 responses in the logs if you run |
@deivid-rodriguez we’re not using gemstash, we instead use an s3 bucket as our backend. |
@ljharb Ok, thanks. I had a recollection that In that case, I have no idea of how setting up an s3 bucket as a backend works with |
Gemstash recently added support for a s3 backend but that is not yet released 😬 |
I'll go ahead and close this since we haven't managed to figure out the root cause of your usage of bundler being faster with For now, let's focus on rubygems/gemstash#72, which is the one issue I have found out about from this ticket :) |
Describe the problem as clearly as you can
At my company,
--full-index
is used to improve performance when fetching gems from S3 buckets. However, there seems to be no environment variable or config file approach to make this be the default, so engineers have to remember to use it manually.(https://stackoverflow.com/questions/14263588/how-to-always-run-bundle-install-with-the-full-index-option asks the same question)
Post system independent steps to reproduce the problem
N/A
Which command did you run?
bundle install --full-index
What were you expecting to happen?
N/A
What actually happened?
N/A
If not included with the output of your command, run
bundle env
and paste the output belowN/A
Is there any way to make this (and perhaps other options) configurable in a way that can be stored in a git repo, or as part of an environment?
The text was updated successfully, but these errors were encountered: