aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorSilvio Rhatto <rhatto@riseup.net>2010-05-08 22:31:02 -0300
committerSilvio Rhatto <rhatto@riseup.net>2010-05-08 22:31:02 -0300
commit35e09a5ba3341a5bcc1bb1604f1b1d78a1fb4089 (patch)
tree511ef3ab27450ab6fbfe710a80c99fb0a9be81cd /README
parentd0d0b7e0ba06e98a754e5acf671df313f8f1bb23 (diff)
downloadkeyringer-35e09a5ba3341a5bcc1bb1604f1b1d78a1fb4089.tar.gz
keyringer-35e09a5ba3341a5bcc1bb1604f1b1d78a1fb4089.tar.bz2
Adding 'options' an 'newkeys' commands
Diffstat (limited to 'README')
-rw-r--r--README14
1 files changed, 14 insertions, 0 deletions
diff --git a/README b/README
index 1bbd7e4..4e6c6bc 100644
--- a/README
+++ b/README
@@ -89,6 +89,20 @@ Keyringer comes with a simple git wrapper to ease common management tasks:
keyringer <keyring> git push keyringer master
keyringer <keyring> git pull
+Managing puppet node keys
+-------------------------
+
+Keyringer is able to manage node keys for puppet nodes. First add the puppet
+main and key folders into your keyring configuration:
+
+ keyringer <keyring> options add PUPPET=/path/to/puppet/config
+ keyringer <keyring> options add PUPPET_KEYS=/path/to/puppet/keys
+
+Then you just need to issue the following command every time you have to create
+keys for new nodes:
+
+ keyringer <keyring> newkeys puppet
+
Notes
-----