summaryrefslogtreecommitdiff
path: root/doc/forum/how_to_install_a_cluster_with_propellor/comment_1_e6860056989da82fd7cd8f374e209548._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/forum/how_to_install_a_cluster_with_propellor/comment_1_e6860056989da82fd7cd8f374e209548._comment')
-rw-r--r--doc/forum/how_to_install_a_cluster_with_propellor/comment_1_e6860056989da82fd7cd8f374e209548._comment3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/forum/how_to_install_a_cluster_with_propellor/comment_1_e6860056989da82fd7cd8f374e209548._comment b/doc/forum/how_to_install_a_cluster_with_propellor/comment_1_e6860056989da82fd7cd8f374e209548._comment
index 20d4b828..571970df 100644
--- a/doc/forum/how_to_install_a_cluster_with_propellor/comment_1_e6860056989da82fd7cd8f374e209548._comment
+++ b/doc/forum/how_to_install_a_cluster_with_propellor/comment_1_e6860056989da82fd7cd8f374e209548._comment
@@ -60,7 +60,8 @@ could be used on any number of hosts:
When you change your propellor config.hs, you need a way to trigger the
nodes to update. Propellor has a couple of different ways to do this;
you could just use Propellor.Property.Cron.runPropellor to run it periodically
-from cron on all the nodes.
+from cron on all the nodes. (With a central git repository holding the
+propellor configuration, naturally.)
Or you could run propellor --spin against all the hosts in the
cluster to push out a change. (It would be a nice enhancement to make