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

Document how to add separate trusted-host values in the pip config. #7803

Closed
stonecharioteer opened this issue Feb 28, 2020 · 0 comments · Fixed by #7918
Closed

Document how to add separate trusted-host values in the pip config. #7803

stonecharioteer opened this issue Feb 28, 2020 · 0 comments · Fixed by #7918
Labels
auto-locked Outdated issues that have been locked by automation state: awaiting PR Feature discussed, PR is needed type: docs Documentation related

Comments

@stonecharioteer
Copy link

It is not entirely obvious how to add multiple hosts to the trusted-hosts section of the config file. In an enterprise, it becomes important to trust pypi.org and an internal host providing a PYPI registry such as that provided by Jfrog Artifactory.

An appropriate section for this would be in the user-guide.

It already contains an example detailing how to add multiple URLs to find-links like so:

[global]
find-links =
    http://download.example.com

[install]
find-links =
    http://mirror1.example.com
    http://mirror2.example.com

However, the way trusted-host is named suggests that only one host can be trusted at any point of time. This is not true since the CLI can be used as:

pip install --trusted-host pypi.org --trusted-host artifactory.mydomain.com virtualenv

That would suggest to an experienced user that:

[install]
trusted-host = 
    https://pypi.org
    https://artifactory.mydomain.com

Furthermore, searching for this option points to this SO question and answer..

Newer users would benefit from having this documented clearly somewhere, since people struggle with using pip in an enterprise situation where SSL errors are a dime a dozen.

@triage-new-issues triage-new-issues bot added the S: needs triage Issues/PRs that need to be triaged label Feb 28, 2020
@uranusjr uranusjr added state: awaiting PR Feature discussed, PR is needed type: docs Documentation related and removed S: needs triage Issues/PRs that need to be triaged labels Feb 28, 2020
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label May 5, 2020
@lock lock bot locked as resolved and limited conversation to collaborators May 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation state: awaiting PR Feature discussed, PR is needed type: docs Documentation related
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants