summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authordosire <sytses@gmail.com>2014-03-18 16:24:49 +0100
committerdosire <sytses@gmail.com>2014-03-18 16:24:49 +0100
commit257aa851d27076453b2dcfee2cc77a75f0e05acf (patch)
treea9432b1cbf249d63315fa1801c007f3991fa03eb
parent0aa389b4911221e0ec5730d5342a1c59f37a8015 (diff)
downloadgitlab-ce-257aa851d27076453b2dcfee2cc77a75f0e05acf.tar.gz
Deploy key needed documentation.
-rw-r--r--doc/ssh/deploy_keys.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/ssh/deploy_keys.md b/doc/ssh/deploy_keys.md
new file mode 100644
index 00000000000..245d71ed9a5
--- /dev/null
+++ b/doc/ssh/deploy_keys.md
@@ -0,0 +1,7 @@
+Deploy keys allow read-only access one or multiple projects with a single SSH key.
+
+This is really useful for cloning repositories to your Continuous Integration (CI) server. By using a 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'. You need to be the owner of the deploy key to see it in this list.