cdist configuration management Latest manual: https://www.cdi.st/manual/latest/ Home page: https://www.cdi.st
Find a file
Steven Armstrong c441f68c9c more /etc/hosts magic to ease development
Signed-off-by: Steven Armstrong <steven.armstrong@inf.ethz.ch>
2011-03-03 08:44:03 +01:00
bin ensure no conf/conf is created (ln -s src dst/conf createst dst/conf/src if conf exists as a dir) 2011-03-02 23:34:19 +01:00
conf more /etc/hosts magic to ease development 2011-03-03 08:44:03 +01:00
doc
.gitignore
HACKERS_README
Makefile
README
REAL_README
TODO-1.0

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:

   % rm -rf /tmp/localhost && ./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}"