summaryrefslogtreecommitdiff
path: root/doc/centralized_git_repository.mdwn
diff options
context:
space:
mode:
authorJoey Hess2014-11-18 21:18:26 -0400
committerJoey Hess2014-11-18 21:18:26 -0400
commitaa3f31940b544e528a5eb3d2e9825a703a8b5013 (patch)
tree0a14bfdf3be969f6029fb54f0c95e2e06ae7d40d /doc/centralized_git_repository.mdwn
parenta19f01a508747fb1f04849616422d1530e8ec2da (diff)
parentb964b4836321832ad8d3be7268fd3af9ed8f5ea8 (diff)
Merge branch 'joeyconfig'
Diffstat (limited to 'doc/centralized_git_repository.mdwn')
-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: