You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow declaring override remotes on a RubyGems source
A `source` may declare one or more `overrides:` — secondary
RubyGems-compatible repositories that supply alternate builds (for
example, prebuilt binaries) of gems that already exist in the primary
source.
source "https://rubygems.org", overrides: ["https://build-farm.example.com"]
Override remotes are consulted only for gems that are also present in
the primary source; they cannot introduce new gems. When an override
publishes a spec whose name and version match one in the primary
source, that spec is preferred for installation if it is compatible
with the local platform. If no matching build is available, or
fetching the override fails (authentication, SSL, or network errors),
Bundler falls back to the primary source.
Override remotes are recorded in `Gemfile.lock` under `override:` lines:
GEM
remote: https://rubygems.org/
override: https://build-farm.example.com/
specs:
IRL Testing:
This can be exercised against Kou's precompiled-gems build farm
hosted on Cloudsmith. The only build target currently published there
is Ruby 4.0 on amd64 Ubuntu 24.04 — on any other platform the
override is skipped and Bundler falls back to the primary source.
source "https://rubygems.org",
overrides: ["https://dl.cloudsmith.io/public/rubygems-precompiled-gems/ruby-4-0-amd64-ubuntu-24-04/ruby/"]
# Precompiled binaries are available on the override remote:
gem "json"
gem "openc3"
gem "io-event"
# Not in the override; fall back to rubygems.org and compile
# from source:
gem "nokogiri"
gem "rails"
0 commit comments