|
|
| Line 16: |
Line 16: |
| </source> | | </source> |
| </blockquote><!-- PR/issue filters --> | | </blockquote><!-- PR/issue filters --> |
|
| |
| == Deploy Keys ==
| |
| <blockquote>
| |
| you can generate keys to provide read-only, or read-write access to a repo.
| |
|
| |
| <source lang="bash">
| |
| ssh-keygen -t ed25519 # a strong key
| |
| </source>
| |
|
| |
| <source lang="yaml">
| |
| https://github.com/<you>/<repo>/settings/keys/new # url to add new deploykey
| |
| </source>
| |
|
| |
| next we'll create entries within our ssh config for the repo.
| |
|
| |
| Create an `alias` for github.com, that will identify which deploykey you'll
| |
| be using here.
| |
| <source lang="ini">
| |
| Host <alias-for-your-repo> github.com
| |
| HostName github.com
| |
| IdentityFile /home/you/.ssh/deploykey
| |
| User git
| |
| </source>
| |
|
| |
|
| |
| Finally, clone the git repository using your alias instead of github.com.
| |
| <source lang="bash">
| |
| git clone <alias-for-your-repo>:<you>/<repo>
| |
| </source>
| |
|
| |
| {{ NOTE |
| |
| Your alias must be a word, not a full address. Some examples:
| |
|
| |
| * git will not recognize <code>myrepo:/you/myrepo</code> as an alias
| |
| * your alias cannot resolve to your repo ex: <code>git clone {alias}</code> is not sufficient. You will need to use <code>git clone {alias}:you/repo</code>.
| |
| }}
| |
| </blockquote><!-- deploy keys -->
| |
