summaryrefslogtreecommitdiff
path: root/doc/automated_spins.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/automated_spins.mdwn')
-rw-r--r--doc/automated_spins.mdwn26
1 files changed, 13 insertions, 13 deletions
diff --git a/doc/automated_spins.mdwn b/doc/automated_spins.mdwn
index e8f44c75..34f04683 100644
--- a/doc/automated_spins.mdwn
+++ b/doc/automated_spins.mdwn
@@ -61,19 +61,19 @@ spin some other hosts.
Using a conductor host has many benefits over a centralized git
repository and cron:
-1. Private data, set with `propellor --set`, is gpg encrypted, and
- hosts cannot decrypt it when their cron job pulls changes from
- the central repository. So after updating the private data of a host,
- you still need to manually run `propellor --spin $HOST`. A conductor
- avoids this problem.
-2. You have to wait a while for a change you commit to be
- deployed by cron. It would be nice to be able to run "propellor"
- once and have it update all your hosts immediately.
-3. When there's a problem, a cron job can hide it, while if you're
- running propellor yourself, you can notice the problem more easily.
-4. You might want to update hosts in a specific order. For example,
- update your dns server last. Cron jobs can't do this, but conductors
- can.
+* Private data, set with `propellor --set`, is gpg encrypted, and
+ hosts cannot decrypt it when their cron job pulls changes from
+ the central repository. So after updating the private data of a host,
+ you still need to manually run `propellor --spin $HOST`. A conductor
+ avoids this problem.
+* You have to wait a while for a change you commit to be
+ deployed by cron. It would be nice to be able to run "propellor"
+ once and have it update all your hosts immediately.
+* When there's a problem, a cron job can hide it, while if you're
+ running propellor yourself, you can notice the problem more easily.
+* You might want to update hosts in a specific order. For example,
+ update your dns server last. Cron jobs can't do this, but conductors
+ can.
Conductors are configured using the
[Propellor.Property.Conductor module](http://hackage.haskell.org/package/propellor/docs/Propellor-Property-Conductor.html).