cdist configuration management Latest manual: https://www.cdi.st/manual/latest/ Home page: https://www.cdi.st
Find a file
Nico Schottelius c466435cb7 cleanup todo for documentation
Signed-off-by: Nico Schottelius <nico@kr.ethz.ch>
2011-03-03 10:54:38 +01:00
bin provide __global for manifests and codegen 2011-03-03 10:37:11 +01:00
conf beautify output 2011-03-03 09:47:02 +01:00
doc cleanup naming in doc 2011-03-03 09:50:48 +01:00
.gitignore
HACKERS_README hackers readme does not need rm -rf anymore 2011-03-03 09:49:19 +01:00
Makefile finish cdist-manifest.text 2011-02-26 20:41:33 +01:00
README
REAL_README begin to redefine installation process 2011-02-26 11:51:59 +01:00
TODO-1.0 cleanup todo for documentation 2011-03-03 10:54:38 +01:00

cat << eof

Hey hackers,

cdist has not been published, you're accessing a early in developent
code.

Do not believe anything written in cdist, besides what's written in this file
(everything else may be future stuff for the initial release).

   -- Nico, 20101201


## Conventions

- All variables exported by cdist are prefixed with a double underscore (__)
- All cdist-internal variables are prefixed with __cdist_ and are generally not exported.

## Running cdist when developing

This file is suitable for execution and saving the objects and
explorers from cdist. I usually do it like this:

   % ./HACKERS_README

################################################################################
eof

set -x
# Tell the user what we do, so this script makes sense during execution

# prepare use (only from top level directory)
export PATH="$PATH:$(pwd -P)/bin"
export __cdist_conf_dir="$(pwd -P)/conf"

# Allow user to supply hostname
target="${1:-localhost}"

# And use hostname as basedir (dangerous, but hackers know what they do)
export __cdist_local_base_dir="/tmp/$target"

# Run the real script
cdist-deploy-to "$target"

# Display results
find "${__cdist_local_base_dir}"