Table of Contents
Deploy configurations to the specified host, as configured in the initial +
Table of Contents
Deploy configurations to the specified host, as configured in the initial manifest. This script triggers the execution of several other scripts, in so called stages. It is intented to run either from the command line or from cron.
If the environment variable cdist_conf_dir is not set, the
configuration is read from <git-checkout>/conf. The local output directory can
@@ -10,6 +10,8 @@ cdist(7)
Table of Contents Welcome dear hacker! I invite you to a tour of pointers to
+ Table of Contents Welcome dear hacker! I invite you to a tour of pointers to
get into the usable configuration mangament system, cdist. The first thing to know is probably that cdist is brought to
you by people who care about how code looks like and who think
twice before merging or implementing a feature: Less features
with good usability are far better than the opposite. IF you are interested in how cdist internally works, you can open
bin/cdist-config and bin/cdist-deploy-to in your favorite editor and
read the scripts bin/cdist-deploy-to calls. The magnificent HACKERS_README
-may be of great help as well. If something should be better done or needs to fixed, add the word FIXME
+nearby, so grepping for FIXME gives all positions that need to be fixed. If you did some cool changes to cdist, which you value as a benefit for
everybody using cdist, you’re welcome to propose inclusion into upstream. There are though some requirements to ensure your changes don’t break others
work nor kill the authors brain: As soon as your work meets these requirements, you can contact me
(IRC, Mailinglist, Phone, RFC 1149) and I’ll check your code before
-including it. Submitting a type works as described above, with the additional requirement
+including it. Submitting a type works as described above, with the additional requirement
that a corresponding manpage named man.text in asciidoc format with
the manpage-name "cdist-type__NAME" is included in the type directory
AND asciidoc is able to compile it (i.e. do NOT have to many "=" in the second
-line). This reference summarises This reference summarises Table of Contents# Ensure zsh is installed
+__package_pkg_openbsd zsh --state installed
+
+# Ensure vim is installed, use flavor no_x11
+__package_pkg_openbsd vim --state installed --flavor no_x11
+
+# If you don't want to follow pythonX packages, but always use python
+__package_pkg_openbsd python --state installed --name python2
+
+# Remove obsolete package
+__package_pkg_openbsd puppet --state removed