this post was submitted on 06 May 2024
34 points (92.5% liked)
Linux
48323 readers
648 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's a blessing and a curse. I have two gitlab accounts on the same server - private and work. I can't use the same key for both as the key is used to distinguish git users, and git doesn't make it easy to select which key you want to use to pull or clone particular repo.
git config core.sshCommand 'ssh -i <path to desired key>'
Hmm, with a similar technique one could even create git command aliases for running git with specific ssh private keys
Better than that, git config supports conditional includes, based on a repo URL or path on disk. So you can have a gitconfig per organization or whatever, which specifies an sshCommand and thus an ssh key.
Just a thought: why don't you just use two different aliases for the Server in your
.ssh/config
with your two differing ssh keys, that way you can just use two different "hostnames" that have different ssh keys specifiedI could but then i can't simply copy the "clone" url from the projects page without editing it.
I think the best solution for me may be to have a separate user account in the OS for work and personal projects. That way i can just log off at the end of the day and use personal account for personal stuff.
You might not even have to log out: Just change the user in the terminal:
su - user2
You can tell git to use a specific key for each repo. I have the same situation as you and this is how I handle it.
https://superuser.com/questions/232373/how-to-tell-git-which-private-key-to-use