cleanup homepage && function
Signed-off-by: Nico Schottelius <nico@kr.ethz.ch>
This commit is contained in:
parent
d98bb4043c
commit
8e27c9d70f
2 changed files with 26 additions and 6 deletions
30
cdist.mdwn
30
cdist.mdwn
|
@ -9,12 +9,34 @@ It is inspired by both of those tools:
|
|||
|
||||
### Principles
|
||||
|
||||
cdist is more
|
||||
cdist is
|
||||
|
||||
- reuse of unix, no need for perl^Wruby
|
||||
- shell
|
||||
* unix, reuse of tools, no need for high level scripting language interpreter
|
||||
|
||||
### Requirements
|
||||
|
||||
* A posix like shell
|
||||
|
||||
## How cdist works
|
||||
|
||||
### Exploring your system
|
||||
|
||||
cdist analyses the system to apply the configuration on and
|
||||
selects the right backends. You can use ***cdist-explore*** to
|
||||
the results of the explore functions.
|
||||
|
||||
### Applying the configuration
|
||||
|
||||
cdist looks for the configuration to apply on the local host
|
||||
and applies it using ***cdist-apply***.
|
||||
|
||||
### Managing many hosts
|
||||
|
||||
Whereas ***cdist-apply*** manages one host, ***cdist-deploy***
|
||||
applies the configuration on enabled hosts.
|
||||
|
||||
## How to use cdist?
|
||||
|
||||
### Unsupported stuff?
|
||||
|
||||
## What do I need [from puppet?]
|
||||
|
||||
|
|
|
@ -25,6 +25,4 @@
|
|||
cdist_package_select_backend()
|
||||
{
|
||||
echo "cdist_package_backend_$(cdist_explore_pkg_system)"
|
||||
|
||||
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue