The latest articles on DEV Community by Papa Pathé SENE (@papepathe). https://dev.to/papepathe https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F63849%2F28af95f3-89f3-48b5-942c-781c6bd7d315.jpeg https://dev.to/papepathe en Papa Pathé SENE Tue, 28 Jul 2020 16:13:15 +0000 https://dev.to/papepathe/per-project-git-ssh-keys-1i6h https://dev.to/papepathe/per-project-git-ssh-keys-1i6h <p>As a professional software developer you work on different projects for distributed clients. </p> <p>You have to deal with many source code management services and ssh keys. </p> <p>For my case i have a professional ssh key and a personal one. I would like to be able to just run git push or pull without specifying the ssh-key to use and git will figure out the rest.</p> <h2> First approach </h2> <p>We can use the environment variable to switch the ssh-key used by git the authenticate push &amp; pull requests.<br> </p> <div class="highlight"><pre class="highlight shell"><code><span class="nv">GIT_SSH_COMMAND</span><span class="o">=</span><span class="s2">"ssh -i /path/to-your/ssh-key"</span> git push your-origin your-branch </code></pre></div> <h2> Second approach </h2> <p>We all agree that it's boring to always specify the ssh key. Thanks to the community, git has a sshCommand configuration variable. We will use it and configure a per project ssh key.<br> </p> <div class="highlight"><pre class="highlight shell"><code>git config core.sshCommand <span class="s2">"ssh -i /path/to-your/ssh-key"</span> </code></pre></div> <h2> References </h2> <p><a href="https://git-scm.com/docs/git#Documentation/git.txt-codeGITSSHCOMMANDcode">GIT_SSH_COMMAND</a><br> <a href="https://git-scm.com/docs/git-config#Documentation/git-config.txt-coresshCommand">git config sshCommand</a></p> git github ssh gitlab