aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorMicah Anderson <micah@riseup.net>2010-12-08 22:24:24 -0500
committerMicah Anderson <micah@riseup.net>2010-12-08 22:24:24 -0500
commitfbb291ed19eeb9a64d4aed78c48d221315da7866 (patch)
treeb13729bc1da7bc7d7c72bc11a5531782d4a31f01 /README
parentd9ccf2a99b4af1430ba6fecdecde9737d89fa674 (diff)
downloadpuppet-apt-fbb291ed19eeb9a64d4aed78c48d221315da7866.tar.gz
puppet-apt-fbb291ed19eeb9a64d4aed78c48d221315da7866.tar.bz2
add apticron support.
Why apticron, when we have cron-apt already? Some people have different preferences, we use apticron along with the upgrade_package functionality in this module. I know someone who uses cron-apt to run the upgrades, but apticron for notifications, because apticron's notifications are much nicer (cron-apt just gives you the output of apt-get upgrade)
Diffstat (limited to 'README')
-rw-r--r--README18
1 files changed, 18 insertions, 0 deletions
diff --git a/README b/README
index 109c92a..355379b 100644
--- a/README
+++ b/README
@@ -162,6 +162,24 @@ The apt class sets up most of the documented functionality. To use
functionality that is not enabled by default, you must include one of
the following classes.
+apt::apticron
+-------------
+
+When you include this class, apticron will be installed, with the following
+defaults, which you are free to change before you include the class:
+
+ $apticron_ensure_version = "present"
+ $apticron_email = "root"
+ $apticron_config = "apt/${operatingsystem}/apticron_${lsbrelease}.erb"
+ $apticron_diff_only = "1"
+ $apticron_listchanges_profile = "apticron"
+ $apticron_system = false
+ $apticron_ipaddressnum = false
+ $apticron_ipaddresses = false
+ $apticron_notifyholds = "0"
+ $apticron_notifynew = "0"
+ $apticron_customsubject = ""
+
apt::cron::download
-------------------