manifest, not initial

Signed-off-by: Nico Schottelius <nico@brief.schottelius.org>
This commit is contained in:
Nico Schottelius 2012-01-16 18:11:28 +01:00
parent a9162bd0e8
commit c8e4d51396
4 changed files with 26 additions and 21 deletions

View file

@ -1,7 +1,6 @@
- write tutorial - write tutorial
- containing many links?! - containing many links?!
- quickstart - cdist-manifest
- cdist-environment/startup/initial-setup (setup env)
- cdist-type - cdist-type
- ... - ...
- cdist-hacker - cdist-hacker

View file

@ -136,7 +136,6 @@ The following **.git/config** is taken from a a real world scenario:
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Have a look at git-remote(1) to adjust the remote configuration, which allows Have a look at git-remote(1) to adjust the remote configuration, which allows
you to push certain branches to certain remotes.
MULTI DEVELOPERS/DIFFERENT TRUST RELATIONSHIP/CENTRAL SERVER APPROACH MULTI DEVELOPERS/DIFFERENT TRUST RELATIONSHIP/CENTRAL SERVER APPROACH

View file

@ -5,7 +5,20 @@ Nico Schottelius <nico-cdist--@--schottelius.org>
NAME NAME
---- ----
cdist-manifest - Define types to be used cdist-manifest - Using types
DESCRIPTION
-----------
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
the parameters are exactly the same.
In general, manifests are used to define which types are used depending
on given conditions.
DEFINE STATE IN THE INITIAL MANIFEST DEFINE STATE IN THE INITIAL MANIFEST
@ -47,23 +60,15 @@ command. Use **ls conf/type** to get a list of available types. If you have
setup the MANPATH correctly as, you can use **man cdist-reference** to access setup the MANPATH correctly as, you can use **man cdist-reference** to access
the reference with pointers to the manpages. the reference with pointers to the manpages.
INITIAL VS. TYPE MANIFEST
-------------------------
DESCRIPTION MANAGING YOUR OWN CONFIGURATION
-----------
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
the parameters are exactly the same.
In general, manifests are used to define which types are used depending
on given conditions.
EXAMPLE
------- EXAMPLES
--------
The initial manifest may for instance contain the following code: The initial manifest may for instance contain the following code:
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
@ -106,10 +111,14 @@ require="__file/etc/cdist-configured __link/tmp/cdist-testfile" \
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
If you do not specify
FIXME: autorequire
SEE ALSO SEE ALSO
-------- --------
- cdist-type(7) - cdist-type(7)
- cdist-tutorial(7)
COPYING COPYING

View file

@ -22,11 +22,9 @@ cdist-quickstart::
cdist-bootstrap:: cdist-bootstrap::
The comprehensive guide to your first cdist installation [beginner] The comprehensive guide to your first cdist installation [beginner]
cdist-initial-manifest:: cdist-manifest::
Learn how to define which hosts get which configurations [beginner] Learn how to define which hosts get which configurations [beginner]
MANAGING YOUR OWN CONFIGURATION
cdist-type:: cdist-type::
Understand how types are working and created [intermediate] Understand how types are working and created [intermediate]