option to specify ssh keys when installing
See original GitHub issueI have a couple private repos on github that I install by doing pip install git+ssh://://git@github.com/whatever/repo
This works great when installing into a virtualenv, but on a single purpose server you want to install it globally. That meas you have to use sudo, which also means pip will try to use the root user’s ssh keys, which is probably not added to your github repository. It would be nice to have a --key argument or something where you can specify the ssh key path to use for such operations. It sucks to have to backup the root’s ssh directory, copy over mine, then install, then restore each time.
Issue Analytics
- State:
- Created 13 years ago
- Reactions:2
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Set up SSH public key authentication to connect to a remote ...
Set up public key authentication using SSH on a Linux or macOS computer · From command-line options · From the user's client configuration...
Read more >How To Configure SSH Key-Based Authentication on a Linux ...
The first step to configure SSH key authentication to your server is to generate an SSH key pair on your local computer. To...
Read more >How To Set up SSH Keys on a Linux / Unix System - nixCraft
Copy and install the public ssh key using ssh-copy-id command on a Linux or Unix server. Add yourself to sudo or wheel group...
Read more >The Ultimate Guide to SSH - Setting Up SSH Keys
Welcome to our ultimate guide to setting up SSH (Secure Shell) keys. This tutorial will walk you through the basics of creating SSH...
Read more >Tutorial: How to Set Up SSH Keys - Teleport
So what is the recommended SSH key generation algorithm? The two most popular options for key generation are either rsa or ed25519 ....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jeffrey-cochran Well, no-one contributed a patch, or put much effort into trying to make a strong case for adding the feature. The pip maintainers are all volunteers, and have their own priorities (not all of which revolve around pip!), so if community members feel a feature is useful, they need to be prepared to contribute.
Closing the issue helps us to focus on things where there is a realistic possibility of something getting implemented. A tracker with masses of unresolved issues is harder to manage, reducing even further the amount of time and motivation available to the developers.
I appreciate that a resolution of “we’re not going to address this” is not your preferred outcome, but I doubt that an open issue that gets ignored is any likely to suit you.
Disappointed this was closed. @pfmoore thanks. I understand. I hold no personal grudge and greatly value the features that folks do have time to implement. I’m commenting to make it known that at least one more user finds this valuable enough to mention it.