cdist configuration management Latest manual: https://www.cdi.st/manual/latest/ Home page: https://www.cdi.st
Find a file
Nico Schottelius 711fea9e7e [DOC] cleanups
Signed-off-by: Nico Schottelius <nico@kr.ethz.ch>
2011-02-19 02:02:21 +01:00
bin cdist-config broken 2011-02-17 17:46:18 +01:00
conf begin to cleanup stages document 2011-02-19 00:01:39 +01:00
doc [DOC] cleanups 2011-02-19 02:02:21 +01:00
.gitignore ignore generated manpages 2011-02-19 01:52:32 +01:00
HACKERS_README shrink hackers readme, allow cdist-deploy-to to be hacked 2011-02-17 16:50:44 +01:00
Makefile [DOC] cleanups 2011-02-19 02:02:21 +01:00
README Describe latest features 2011-02-02 21:49:01 +01:00
REAL_README +" 2011-02-18 08:49:28 +01:00
TODO-1.0 todo: finished 5 stages, go to doc now 2011-02-19 00:10:07 +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

cdist-deploy-to localhost

find "${base}"