Explore >> Select a destination
|
You are here 
|
nbailey.ca | ||
| | | | |
rolisz.ro
|
|
| | | | | As a freelancer, I work for many clients, who have their source code in many different places, often self hosted. I generally create new SSH keys for each separate platform. Unfortunately, Git doesn't provide an option for what keys to use, you have to configure this in the ~/.ssh/config | |
| | | | |
zzamboni.org
|
|
| | | | | via http://www.freshblurbs.com/blog/2013/06/22/github-multiple-ssh-keys.html#tldr Since Github doesn't allow us to reuse an SSH Key, the only sane solution is to jump through some hoops and generate + use multiple keys on the server itself. Let's look at some effective approaches of doing that. Short version: define multiple hosts in the SSH config file for each repository, which use different SSH keys, then you can assign different deploy keys to each repo. But read the whole article for the full details. | |
| | | | |
ianduffy.ie
|
|
| | | | | Learn how to seamlessly switch between work and personal GitHub accounts using SSH, GPG, and SSH agent configurations. This guide walks you through setting up 1Password for secure key management, configuring Git for different identities, and automating the process to enhance your development workflow. | |
| | | | |
ar.al
|
|
| | | I'm setting up my new XPS 13 running Pop!_OS and one of the things I always have to do on any new machine is to configure git. So, both for my own reference and in case it helps anyone else, here's a list of things I do to set up git: Set up my identity (used in commits, tags, etc.) git config --global user.name "Aral Balkan" git config --global user.email mail@ar. | ||
