Deconst, Integrated

docker-compose configuration that instantiates a single "pod" of Deconst services, with all of the debug settings cranked up to full. It's useful for:

Integration testing of Deconst components, before you commit to master and
Previewing local content or control repository changes when the deconst client is busted

Prerequisites

Install a recent version of Docker for your platform.

If you are on MacOS, stop here and go to Getting Started.

If you are on Windows or Linux, continue:

Install docker-compose. In addition to the curl command they list, you can also install it from homebrew or pip.

Make sure that docker-machine is create and running first.

docker-machine create --driver virtualbox dev

Run eval $(docker-machine env default) in each shell you'll use to interact with Docker.

Getting Started

Clone this repository and cd into the directory where you cloned the repo. Then:

Customize your credentials and other settings. The env settings require knowing your Rackspace Cloud account info and also where you intend to clone the control repo, for example.
```
cp env.example env
${EDITOR} env
```
Launch the services.
```
script/up
```

script/up accepts any parameters that docker-compose up does. Notably, you can use script/up -d to launch services in the background.

Manual Alternative

If you prefer, you can manually run each docker container with:

# generate an admin API key for the content service
APIKEY=$(hexdump -v -e '1/1 "%.2x"' -n 128 /dev/random)
echo "Content Service Admin API Key:" $APIKEY

# start content service dependencies
docker run -d --name elasticsearch elasticsearch:1.7
docker run -d --name mongo mongo:2.6

# build and deploy the content service
cd ${CODE_ROOT}/content-service
docker build --tag content-service:dev .
docker run -d -p 9000:8080 \
  -e NODE_ENV=development \
  -e STORAGE=memory \
  -e MONGODB_URL=mongodb://mongo:27017/content \
  -e ELASTICSEARCH_HOST=http://elasticsearch:9200/ \
  -e ADMIN_APIKEY=${APIKEY} \
  --link mongo:mongo \
  --link elasticsearch:elasticsearch \
  --name content \
  content-service:dev script/inside/dev

# build and deploy the presenter service
cd ${CODE_ROOT}/presenter
docker build --tag presenter:dev .
docker run -d -p 80:8080 \
  -e NODE_ENV=development \
  -e CONTROL_REPO_PATH=/var/control-repo \
  -e CONTROL_REPO_URL=... \
  -e CONTROL_REPO_BRANCH=... \
  -e CONTENT_SERVICE_URL=http://content:8080 \
  -e PRESENTED_URL_PROTO=http \
  -e PRESENTED_URL_DOMAIN=support.rackspace.com \
  --link content \
  --name presenter \
  presenter:dev script/dev

Submitting Content

Now the site is running, but you don't have any content submitted, yet. To add some, run the appropriate script/add-* script with the path to your clone of a local content repository.

script/add-sphinx ~/writing/drc/docs-quickstart

script/add-jekyll ~/writing/drc/docs-developer-blog

Updating content or mappings