-
Notifications
You must be signed in to change notification settings - Fork 64.3k
Multiple deploy keys #501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Multiple deploy keys #501
Changes from 1 commit
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
08657ac
Update managing-deploy-keys.md
tarrenj 35d5313
Update managing-deploy-keys.md
tarrenj 6ceecfa
Update managing-deploy-keys.md
tarrenj 3893932
Merge branch 'main' into multiple-deploy-keys
tarrenj efbe8eb
Merge branch 'main' into multiple-deploy-keys
tarrenj f5dbe78
Merge branch 'main' into multiple-deploy-keys
tarrenj 2671463
Merge branch 'main' into multiple-deploy-keys
tarrenj 77e6f3d
Merge branch 'main' into multiple-deploy-keys
tarrenj dfdccd5
Added some edits to draft
martin389 218625f
Merge branch 'main' into multiple-deploy-keys
martin389 1931771
Some small fixes
martin389 69b5545
Rephrased example sentence
martin389 adf8a75
Merge branch 'main' into multiple-deploy-keys
tarrenj 03eeb42
Merge branch 'main' into multiple-deploy-keys
tarrenj 384fa93
Merge branch 'main' into multiple-deploy-keys
tarrenj b7bfb89
Apply suggestions from code review
martin389 b6417be
Rephrasing for easier compatibility
martin389 ae8805a
Added versioning for GHES
martin389 0564ab2
Merge branch 'main' into multiple-deploy-keys
martin389 eca5ebb
Small edit
martin389 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Added some edits to draft
- Loading branch information
commit dfdccd564451b521c999db1d221039e964232378
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -83,31 +83,27 @@ See [our guide on Git automation with tokens][git-automation]. | |
| 7. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository. | ||
| 8. Click **Add key**. | ||
|
|
||
| ##### Multiple Repositories on One Server | ||
| ##### Using multiple repositories on one server | ||
|
|
||
| GitHub does not allow users to reuse deploy keys across multiple repositories, so when a personal key pair is undesirable (such as a deployment server) users have to generate a dedicated key pair for each repository they require. Additionally, Git (currently) does not provide a way of configuring a preferred private key when using ssh remotes. | ||
| If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories. | ||
|
|
||
| ###### Setup | ||
| In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. For example: | ||
|
|
||
| 1. Using your favorite text editor, open up the file at `~/.ssh/config`. If this file doesn't exist, you can create it by entering `touch ~/.ssh/config` in the terminal. | ||
| 2. Create an alias for each repository that points to the git server and assignes the private key: | ||
| ``` | ||
| ```bash | ||
| Host github.amrom.workers.dev-repo-0 | ||
| Hostname github.com | ||
| IdentityFile=/home/user/.ssh/repo-0_deploy_key | ||
|
|
||
| Host github.amrom.workers.dev-repo-1 | ||
| Hostname github.com | ||
| IdentityFile=/home/user/.ssh/repo-1_deploy_key | ||
|
|
||
| Host github.amrom.workers.dev-repo-2 | ||
| Hostname github.com | ||
| IdentityFile=/home/user/.ssh/repo-2_deploy_key | ||
| ``` | ||
|
|
||
| ###### Example Usage | ||
| * `Host github.amrom.workers.dev-repo-0` - The repository's alias. | ||
| * `Hostname github.com` - Configures the alias to use the {% data variables.product.product_name %} server. | ||
| * `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - assigns a private key to the alias. | ||
|
|
||
| To clone a repository with a unique Deploy Key, use the the alias as defined in the `~/.ssh/config`: | ||
| With these entries, you can then use the alias to clone a repository with a unique Deploy Key. For example: | ||
|
|
||
| ``` | ||
| git clone [email protected]:github-user/repo-1.git | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.