Explore >> Select a destination
|
You are here 
|
devintheshell.com | ||
| | | | |
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. | |
| | | | |
fundor333.com
|
|
| | | | | My advance config for git e ssh | |
| | | | |
benji.dog
|
|
| | | | | This may be overkill, but it works on my machine | |
| | | | |
lobsterpot.com.au
|
|
| | | I don't like to write about client situations, but this one seemed worth mentioning for the sake of other people experiencing the same thing, so I asked my client for permission and they agreed. Following an on-prem server reboot, anything that tried to connect to SQL Server on that server, using Windows Authentication, was getting [...] | ||
