vagrant_full.md

#Full Vagrant Development

The platform-ws-services project depends on RethinkDB and Redis.

We have provided a Vagrantfile to ease your development cycle and reduce what dependencies you need to worry about.

Please note: This requires Vagrant 1.5+

##Deploying

In order to provision a deployment issue a:

vagrant up

This will bring up:

• Redis VM running latest version of Redis
• RethinkDB VM running version 2.0.5 of RethinkDB
• A VM which downloads dependencies, runs tests, builds, seeds, and runs the platform-ws-services project

##Using

If everything deployed correctly you should be able to:

source setup-env.sh
curl -u x:$COMPOSE_SERVICE_PASSWORD $COMPOSE_SERVICE_URL/deployments/987654321

and get

{
  "111111": [
    {
      "account": "compose-test",
      "capsule_id": "111111",
      "capsule_name": "redis0",
      "deployment_id": "987654321",
      "name":"redis_role",
      "output": "",
      "status":0
    }
  ]
}

where $COMPOSE_SERVICE_PASSWORD and $COMPOSE_SERVICE_URL are defined in setup-env.sh

##Logs

Stderr and Stdout for the platform-ws-services process will be accessible from within the compose VM at /var/log/platform-ws-services.log as well as locally in the platform-ws-services.log file

So a tail -f [PLATFORM_WS_SERVICES_DIR]/platform-ws-services.log will give you live logs from the deployment

##Developing

You can work within the VM if you want via vagrant ssh compose. But you probably prefer to write code on your own machine with your favorite editors. To do this, just edit the code then perform a vagrant provision compose and the compose VM will test, rebuild and relaunch the new platform-ws-services, as well as reseed the databases.

Note of importance, when provisioning - the default behavior is to set an expiration to Redis keys. Don't panic if you brought up your VM a while ago and all of a sudden you aren't seeing things you think you should. Simply run a vagrant provision compose which will reseed the databases, giving you expected state as given in these docs.

##Of Note

This project was originally built with RethinkDB 2.0.5 and gorethink 1.0.0. The RethinkDB VM is running RethinkDB 2.0.5 and we package the project with gorethink 1.0.0 vendored.

The Vagrantfile is configured to launch the VMs to 10.0.32.2 10.0.32.3 and 10.0.32.4. If you are already on a 10.0.32.x network, you will want to edit the private_network configuration in the Vagrantfile, and update the setup-env.sh script to reflect those changes