First take on refactoring the SSH keys docsdocs/refactor-ssh-keys

- Split ssh/README.md to user/profile/ssh_keys.md and user/project/deploy_keys.md
- Deprecate gitlab-basics/create-your-ssh-keys.md and move its info in user/profile/ssh_keys.md
- Change links in views

1 files changed, 23 insertions, 0 deletions

diff --git a/doc/user/project/deploy_keys.md b/doc/user/project/deploy_keys.md
new file mode 100644
index 00000000000..c9a94389c33
--- /dev/null
+++ b/doc/user/project/deploy_keys.md
@@ -0,0 +1,23 @@
+## Deploy keys
+
+Deploy keys allow read-only access to multiple projects with a single SSH
+key.
+
+This is really useful for cloning repositories to your Continuous
+Integration (CI) server. By using deploy keys, you don't have to setup a
+dummy user account.
+
+If you are a project master or owner, you can add a deploy key in the
+project settings under the section 'Deploy Keys'. Press the 'New Deploy
+Key' button and upload a public SSH key. After this, the machine that uses
+the corresponding private key has read-only access to the project.
+
+You can't add the same deploy key twice with the 'New Deploy Key' option.
+If you want to add the same key to another project, please enable it in the
+list that says 'Deploy keys from projects available to you'. All the deploy
+keys of all the projects you have access to are available. This project
+access can happen through being a direct member of the project, or through
+a group. See `def accessible_deploy_keys` in `app/models/user.rb` for more
+information.
+
+Deploy keys can be shared between projects, you just need to add them to each project.