cdist configuration management Latest manual: https://www.cdi.st/manual/latest/ Home page: https://www.cdi.st
Find a file
Nico Schottelius 45cc072d21 remove cdist-environment, merge into HACKERS_README, update that as well
Signed-off-by: Nico Schottelius <nico@kr.ethz.ch>
2011-02-26 11:38:01 +01:00
bin export __cdist_local_base_dir in cdist-deploy-to for others 2011-02-26 10:42:06 +01:00
conf cleanup issue 2011-02-26 10:44:50 +01:00
doc remove cdist-environment, merge into HACKERS_README, update that as well 2011-02-26 11:38:01 +01:00
.gitignore ignore generated manpages 2011-02-19 01:52:32 +01:00
HACKERS_README remove cdist-environment, merge into HACKERS_README, update that as well 2011-02-26 11:38:01 +01:00
Makefile [DOC] cleanups 2011-02-19 02:02:21 +01:00
README
REAL_README cleanup and remove cdist-design.text 2011-02-26 11:27:53 +01:00
TODO-1.0 remove cdist-environment, merge into HACKERS_README, update that as well 2011-02-26 11:38:01 +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:

   % rm -rf /tmp/localhost && ./HACKERS_README

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

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

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

export __cdist_local_base_dir=/tmp/localhost

target="${1:-localhost}"
cdist-deploy-to "$target"

find "${__cdist_local_base_dir}"