summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJoey Hess2014-11-18 18:56:15 -0400
committerJoey Hess2014-11-18 18:56:15 -0400
commit7299cd73206c47b27a0a80ae9810ca4506942b11 (patch)
treea5dbfa395fcd42e3301faa4c7724fe6c190be40b /doc
parent0b58bc17100eab7f2f41e86a2d3e19796fc3e903 (diff)
expand
Diffstat (limited to 'doc')
-rw-r--r--doc/centralized_git_repository.mdwn8
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/centralized_git_repository.mdwn b/doc/centralized_git_repository.mdwn
index f47aa92e..46cf89e2 100644
--- a/doc/centralized_git_repository.mdwn
+++ b/doc/centralized_git_repository.mdwn
@@ -4,7 +4,13 @@ directly to the host. This makes it easy to get started with propellor.
A central git repository allows hosts to run propellor from cron and pick
up any updates you may have pushed. This is useful when managing several
-hosts with propellor.
+hosts with propellor.
+
+The central repository does not need to be trusted; it can be hosted
+anywhere, and propellor will only accept verified gpg signed git commits
+from it. See [[security]] for details, but this means you can put it
+on github without github being able to 0wn your propellor driven hosts, for
+example.
You can add a central git repository to your existing propellor setup easily: