You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Nico Schottelius a07aafdc88 finish cdist-manifest.text 14 years ago
bin
conf
doc finish cdist-manifest.text 14 years ago
.gitignore prepare manpage generation in makefile 14 years ago
HACKERS_README
Makefile finish cdist-manifest.text 14 years ago
README
REAL_README begin to redefine installation process 14 years ago
TODO-1.0

README

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"

export __cdist_local_base_dir=/tmp/localhost

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

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

# Display results
find "${__cdist_local_base_dir}"