cdist-best-practice - Practices used in real environments
2. PASSWORDLESS CONNECTIONS
It is recommended to run cdist with public key authentication.
This requires a private/public key pair and the entry
"PermitRootLogin without-password" in the sshd server.
See sshd_config(5) and ssh-keygen(1).
3. SPEEDING UP SSH CONNECTIONS
When connecting to a new host, the initial delay with ssh connections
diff --git a/software/cdist/man/cdist-code-run-all.html b/software/cdist/man/cdist-code-run-all.html
index 42712eb7..c835f401 100644
--- a/software/cdist/man/cdist-code-run-all.html
+++ b/software/cdist/man/cdist-code-run-all.html
@@ -1,6 +1,6 @@
-
cdist-code-run executes generated code from a given OBJECT.
The OBJECT must be located below OBJECT_DIR.
TYPE must be either local or remote and determines which
code part is to be executed.
Cdist-config is sourced by cdist programs and provides hints on where to find
types, manifests, etc. Generally speaking, it’s just usable from within the
core and is only of interest for cdist-developers.
3. SEE ALSO
cdist(7)
4. COPYING
Copyright (C) 2010-2011 Nico Schottelius. Free use of this software is
granted under the terms of the GNU General Public License version 3 (GPLv3).
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.
4. ENVIRONMENT
If the environment variable cdist_conf_dir is not set, the
configuration is read from /etc/cdist. The local output directory can
diff --git a/software/cdist/man/cdist-dir.html b/software/cdist/man/cdist-dir.html
index 04720a51..f7e7a2c5 100644
--- a/software/cdist/man/cdist-dir.html
+++ b/software/cdist/man/cdist-dir.html
@@ -1,6 +1,6 @@
-cdist-dir(1)
cdist-dir either pushes a local directory to the target host
or pulls a remote directory from a target host to the local host.
In the push case SRC_DIR is local, in the pull case remote.
In the push case DST_DIR is remote, in the pull case local.
cdist-dir does not cleanup DST_DIR and thus it may contain old
stuff if used multiple times.
cdist-dir does not rely on rsync or other high level tools, because
diff --git a/software/cdist/man/cdist-env.html b/software/cdist/man/cdist-env.html
index 9a2345ce..003c9095 100644
--- a/software/cdist/man/cdist-env.html
+++ b/software/cdist/man/cdist-env.html
@@ -1,6 +1,6 @@
-
cdist-env outputs two strings suitable for usage in your current shell,
so you can use cdist from the checkout. cdist-env essentially helps you
to easily setup PATH and MANPATH.
If you’ve multiple checkouts of cdist and run cdist-env from the various
checkouts, a new run will prepend the last directory, thus ensures you
diff --git a/software/cdist/man/cdist-explorer-run-global.html b/software/cdist/man/cdist-explorer-run-global.html
index 5fb6e080..84184002 100644
--- a/software/cdist/man/cdist-explorer-run-global.html
+++ b/software/cdist/man/cdist-explorer-run-global.html
@@ -1,6 +1,6 @@
-
Explorer are small shell scripts, which will be executed on the target
host. The aim of the explorer is to give hints to types on how to act on the
target system. An explorer outputs the result to stdout, which is usually
a one liner, but may be empty or multi line especially in the case of
diff --git a/software/cdist/man/cdist-hacker.html b/software/cdist/man/cdist-hacker.html
index 20f88b6a..57dda706 100644
--- a/software/cdist/man/cdist-hacker.html
+++ b/software/cdist/man/cdist-hacker.html
@@ -1,6 +1,6 @@
-
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
diff --git a/software/cdist/man/cdist-manifest-run-all.html b/software/cdist/man/cdist-manifest-run-all.html
index 48bf1ed4..52e66da9 100644
--- a/software/cdist/man/cdist-manifest-run-all.html
+++ b/software/cdist/man/cdist-manifest-run-all.html
@@ -1,6 +1,6 @@
-
Manifests exist to define which configurations should be applied to a specific
host as well as to define which configurations should be applied within a
type. Manifests are executed locally and the resulting objects are stored in
an internal database.
The same object can be redefined in multiple different manifests as long as
diff --git a/software/cdist/man/cdist-object-explorer-all.html b/software/cdist/man/cdist-object-explorer-all.html
index 782e485d..e5d3b89a 100644
--- a/software/cdist/man/cdist-object-explorer-all.html
+++ b/software/cdist/man/cdist-object-explorer-all.html
@@ -1,6 +1,6 @@
-
cdist-object-explorer-all - Run type explorer for every object
2. SYNOPSIS
cdist-object-explorer-all HOSTNAME
3. DESCRIPTION
For every object, it checks whether the type has one or more explorers.
If so, the explorers of the type are copied to the target and executed
once per object.
cdist-reference - Variable, path and type reference for cdist
2. DESCRIPTION
Various scripts which are not in the core need information on how
to find information. This manpage summarises the available environment
variables, types and paths and clearifies with part may access which variables.
3. PATHS
If not specified otherwise, all paths are relative to the checkout directory.
conf/
@@ -89,7 +89,89 @@ tmp_dir
which will be removed when the scripts end automatically.
See cdist-config(1).
cdist-remote-explorer-run is executed on the target.
It sets up the variable VARIABLE_NAME to point to the given
EXPLORER_DIR and runs all explorer found in EXPLORER_DIR.
The output of every run explorer is saved into OUT_DIR.
cdist-stages - Stages used during configuration deployment
2. DESCRIPTION
Starting the execution of deployment with cdist-deploy-to(1), cdist passes
through different stages, each can be triggered and debugged on its own.
Reading the source of the cdist-deploy-to executable shous the scripts
responsible for each stage.
3. STAGE 0: INTERNAL PREPERATION
Before running the user facing stages, cdist prepares the target host
diff --git a/software/cdist/man/cdist-type-build-emulation.html b/software/cdist/man/cdist-type-build-emulation.html
index 93f177be..6bf5eafe 100644
--- a/software/cdist/man/cdist-type-build-emulation.html
+++ b/software/cdist/man/cdist-type-build-emulation.html
@@ -1,6 +1,6 @@
-
cdist-type-build-emulation - Build executables for types
2. SYNOPSIS
cdist-type-build-emulation OUT_DIR
3. DESCRIPTION
cdist-type-build-emulation creates a link to cdist-type-emulator
for every TYPE. These links are placed in a OUT_DIR, which
is prepended into $PATH. This way the user can use TYPE in the
manifests like any other executable.
cdist-type-emulator - Emulate type and record parameters and dependencies
2. SYNOPSIS
cdist-type-emulator [TYPE ARGS]
3. DESCRIPTION
cdist-type-emulator is normally called through a link to it of the
name of a specifc type. It saves the given parameters into
a parameters directory and the requirements into a require file.
It checks whether the parameters are valid:
are required parameter given?
diff --git a/software/cdist/man/cdist-type-template.html b/software/cdist/man/cdist-type-template.html
index a71158d7..b21505eb 100644
--- a/software/cdist/man/cdist-type-template.html
+++ b/software/cdist/man/cdist-type-template.html
@@ -1,5 +1,5 @@
-cdist-type-template(1)
This cdist type allows manage ubuntu ppa repositories.
3. REQUIRED PARAMETERS
state
The state the ppa should be in, either "enabled" or "disabled".
diff --git a/software/cdist/man/cdist-type__directory.html b/software/cdist/man/cdist-type__directory.html
index fc5268d1..e2d491c5 100644
--- a/software/cdist/man/cdist-type__directory.html
+++ b/software/cdist/man/cdist-type__directory.html
@@ -1,6 +1,6 @@
-cdist-type__directory(7)
This cdist type allows you to create directories on the target.
3. REQUIRED PARAMETERS
None.
4. OPTIONAL PARAMETERS
group
Group to chgrp to.
diff --git a/software/cdist/man/cdist-type__file.html b/software/cdist/man/cdist-type__file.html
index 3214d419..ef451783 100644
--- a/software/cdist/man/cdist-type__file.html
+++ b/software/cdist/man/cdist-type__file.html
@@ -1,6 +1,6 @@
-cdist-type__file(7)
This cdist type allows you to create files on the target.
3. REQUIRED PARAMETERS
None.
4. OPTIONAL PARAMETERS
group
Group to chgrp to.
diff --git a/software/cdist/man/cdist-type__group.html b/software/cdist/man/cdist-type__group.html
index 75120b18..9d16a7e4 100644
--- a/software/cdist/man/cdist-type__group.html
+++ b/software/cdist/man/cdist-type__group.html
@@ -1,6 +1,6 @@
-cdist-type__group(7)
This cdist type allows you to easily setup /etc/issue.
3. REQUIRED PARAMETERS
None.
4. OPTIONAL PARAMETERS
source
If supplied, use this file as /etc/issue instead of default.
diff --git a/software/cdist/man/cdist-type__key_value.html b/software/cdist/man/cdist-type__key_value.html
index aeee7edd..6d88f26d 100644
--- a/software/cdist/man/cdist-type__key_value.html
+++ b/software/cdist/man/cdist-type__key_value.html
@@ -1,6 +1,6 @@
-cdist-type__key_value(7)
This cdist type allows you to easily setup /etc/motd.
3. REQUIRED PARAMETERS
None.
4. OPTIONAL PARAMETERS
source
If supplied, copy this file from the host running cdist to the target.
diff --git a/software/cdist/man/cdist-type__package.html b/software/cdist/man/cdist-type__package.html
index c2b7d691..d096bac4 100644
--- a/software/cdist/man/cdist-type__package.html
+++ b/software/cdist/man/cdist-type__package.html
@@ -1,6 +1,6 @@
-cdist-type__user(7)