commit | 46ffc41584205b8f3b9fe1000a2f773fd6612217 | [log] [tgz] |
---|---|---|
author | Nicolas LaCasse <nlacasse@google.com> | Tue Nov 04 13:04:04 2014 -0800 |
committer | Nicolas LaCasse <nlacasse@google.com> | Tue Nov 04 13:04:04 2014 -0800 |
tree | 79b2e8bc9041155cf6b15fab8476294a054a10fb | |
parent | fa1607343e1800f4ddbf2d7853853607fab2e2a8 [diff] |
Remove "-new-security-model" flag from wspr startup. This fixes the playground tests. Change-Id: Ifd578751a69b35afb06571a8956e09f9cee56477
Install Docker:
On Goobuntu, we recommend overriding the default graph dir (/var/lib/docker
) to avoid filling up the root filesystem partition, which is quite small. To do so, add the following line to your /etc/default/docker
:
DOCKER_OPTS="${DOCKER_OPTS} -g /usr/local/google/docker"
Start (or restart) the Docker daemon:
$ sudo service docker restart
Build the playground Docker image (this will take a while...):
$ cp ~/.netrc $VEYRON_ROOT/veyron/go/src/veyron.io/playground/builder/netrc $ sudo docker build -t playground $VEYRON_ROOT/veyron/go/src/veyron.io/playground/builder/.
Note: If you want to ensure an up-to-date version of veyron is installed in the Docker image, run the above command with the “--no-cache” flag.
Test your image (without running compilerd):
$ sudo docker run -i playground < /usr/local/google/home/sadovsky/dev/veyron-www/content/playgrounds/code/fortune/ex0-go/bundle.json
Install the playground binaries:
$ veyron go install veyron.io/playground/...
Run the compiler binary as root:
$ sudo $VEYRON_ROOT/veyron/go/bin/compilerd --shutdown=false --address=localhost:8181
Or, run it without Docker (for faster iterations during development):
$ cd $(mktemp -d "/tmp/XXXXXXXX") $ PATH=$VEYRON_ROOT/veyron/go/bin:$PATH compilerd --shutdown=false --address=localhost:8181 --use-docker=false
The server should now be running at http://localhost:8181 and responding to compile requests at http://localhost:8181/compile.
Add ?pgaddr=//localhost:8181
to any veyron-www page to make its embedded playgrounds talk to your server. Add ?debug=1
to see debug info from the builder.