mirror of https://github.com/renovatebot/renovate
ef4d5b2bbf | ||
---|---|---|
.. | ||
__fixtures__ | ||
__snapshots__ | ||
artifacts.spec.ts | ||
artifacts.ts | ||
common.spec.ts | ||
common.ts | ||
extract.spec.ts | ||
extract.ts | ||
gemfile.spec.ts | ||
host-rules.spec.ts | ||
host-rules.ts | ||
index.ts | ||
locked-version.spec.ts | ||
locked-version.ts | ||
readme.md | ||
update-locked.spec.ts | ||
update-locked.ts |
readme.md
Renovate uses the bundler
manager to extract dependencies from Gemfile
and Gemfile.lock
files.
Authenticating private registry
If:
- you need Bundler to authenticate to a private registry
- and that private registry is not on the same host as Renovate (your GitHub/GitLab/etc)
Then you should authenticate Renovate with hostRules
.
For example:
{
"hostRules": [
{
"matchHost": "private-registry.company.com",
"hostType": "rubygems",
"token": "abc123"
}
]
}
Important notes:
hostType
is a required field, sethostType=rubygems
- If you use the same registry for more than one package type, you may need more than one
hostRules
entry - Instead of
token
, you can use ausername
andpassword
To avoid committing raw secrets to your repository, either:
- If self-hosting: add the
hostRules
to your bot config file, instead of the repository configuration file, or - If using the Mend Renovate App: use the
encrypted
config option