On Monday, November 18, 2013 5:37:25 AM UTC+1, stoi...@aol.com wrote:

> I was just in a situation where I had to change a remote repository on 
> github. When I went to deploy my application, I refused to deploy because 
> on the 3 servers it deploys to, the keys were referencing the old 
> repository not the new one. So I had to go on the 3 servers and put the 
> keys in a backup directory under ~/.ssh and generate public keys for each 
> server, and then upload them to the github repository. It seemed pretty 
> inefficient. Is there a better way to handle this? 

Sounds like you want to automate your infrastructure using some 
configuration tool like Puppet or Chef.

Furthermore, you could have all build/servers share one key-pair (which is 
distributed/updated by Puppet). I mean, if any one of them are compromised, 
the attacker got all your source-code anyway, right?

Try googling "distributing ssh keys with puppet", looks like there are a 
lot of interesting material about this.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to