Github Deploy Key Pattern

Kevin John

1/17/24, 5:57 PM

I have a setup as shown in the diagram above, where have a github account which owns a number of private repositories. I have a number of machines in the field that each include some subset of the repositories that I manage. Each repository, on each machine, contains a unique RSA keypair tied to a unique deploy key. I individually assign the core.sshCommand for each repo to use the unique key so I can push and pull from the repository as needed.

This works, but it's very labor intensive since every time I deploy a new machine, I have to generate a new key, add the deploy key to the GitHub, and assign it to local repo via core.sshCommand. Is there an easier way of doing this? Because it seems like a really common pattern but GitHub's security policies sort of forced me into what seems like a very inefficient pattern.

1 + 0

rsa

github

ssh-keys

Score:0

Server

Kevin John

1/18/24, 7:12 PM

It's not going to be a satisfying solution, but I've decided that since the security policies at GitHub don't allow me to work in the way I need to, I am just going to switch to a hosted server on AWS where I can run my own Git server.

+ 0

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Github Deploy Key Pattern

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.