summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Friesel <derf@derf.homelinux.org>2010-02-07 17:15:56 +0100
committerDaniel Friesel <derf@derf.homelinux.org>2010-02-07 17:15:56 +0100
commitdd99af48942d5d67941da212f99b61a3b82754ea (patch)
tree652dfa14be5e6fe2c50e240a401bbd2758f81061
parentffb9802d1ed5a3ac0f710a240d19eaba0fab5498 (diff)
caretaker-setup(7): Add section about deploying caretaker on a client
-rw-r--r--man/7/caretaker-setup.pod16
1 files changed, 16 insertions, 0 deletions
diff --git a/man/7/caretaker-setup.pod b/man/7/caretaker-setup.pod
index 394dd3f..4e64b4b 100644
--- a/man/7/caretaker-setup.pod
+++ b/man/7/caretaker-setup.pod
@@ -68,6 +68,22 @@ Example:
soft .ssh/config ../$etc/config
+=head1 ADDING A CLIENT
+
+Now that you have a package root and some packages, you might start to wonder
+how to actually start using them on some machine.
+
+In theory, this is quite trivial. caretaker ships a B<bootstrap> script in
+F<examples/bootstrap> (again, you can get it from the bare repo with
+C<< git cat-file blob master:examples/bootstrap >>). Execute the script to see
+its help message, then execute it again with the proper arguments on the
+machine on which you want to use caretaker and watch its output.
+
+With the terminology from the previous sections, in most cases you'll need
+C<< ./bootstrap ssh://server/$PKG_ROOT >>.
+If you deploy caretaker on the server containing the package root,
+C<< ./bootstrap /$PKG_ROOT >> will suffice.
+
=head1 SEE ALSO
checklinks(1), ct(1), caretaker(7)