cdist configuration management Latest manual: https://www.cdi.st/manual/latest/ Home page: https://www.cdi.st
Find a file
Nico Schottelius bf94bd1aab no need to export variables
Signed-off-by: Nico Schottelius <nico@kr.ethz.ch>
2011-02-23 09:20:34 +01:00
bin no need to export variables 2011-02-23 09:20:34 +01:00
conf remove failing objects from initial manifest 2011-02-23 09:15:38 +01:00
doc Revert "nicos next stuff todo" 2011-02-22 23:08:26 +01:00
.gitignore
HACKERS_README
Makefile
README
REAL_README
TODO-1.0 +todo 1.0 2011-02-22 15:27:06 +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


What you can do so far: (executed from top level directory)

The following code will get executed if you run this README,
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_config="$(pwd -P)/conf"

# Change paths so we can debug stuff :-)
base=/tmp/localhost
export __cdist_out_objects=${base}/objects
export __cdist_out_explorers=${base}/explorers
export __cdist_out_execs=${base}/exec

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

find "${base}"