webtry: More README doc cleanups.

Puts it much more in sync with the README in perf/.

BUG=None
TEST=None
R=jcgregorio@google.com

Review URL: https://codereview.chromium.org/615313002
This commit is contained in:
tfarina 2014-10-01 09:18:57 -07:00 committed by Commit bot
parent cda6885f0a
commit b1dfb03685

View File

@ -1,10 +1,11 @@
WebTry WebTry Server
====== =============
Allows trying out Skia code in the browser. Run a local webserver Allows trying out Skia code in the browser. Run a local webserver
and from the pages it serves try out Skia code and see the results and from the pages it serves try out Skia code and see the results
immediately. To make sandboxing easier this must be built w/GPU off. immediately. To make sandboxing easier this must be built w/GPU off.
Running Locally Running Locally
=============== ===============
@ -19,8 +20,9 @@ Then visit http://localhost:8000 in your browser.
Only tested under linux, doubtful it will work on other platforms. Only tested under linux, doubtful it will work on other platforms.
Full Server Setup
================= Server Setup
============
Create a GCE instance: Create a GCE instance:
@ -38,24 +40,28 @@ SSH into the instance:
gcutil --project=google.com:skia-buildbots ssh --ssh_user=default skia-webtry-b gcutil --project=google.com:skia-buildbots ssh --ssh_user=default skia-webtry-b
Do once Do the first time
------- =================
The following things only need to be done once The following things only need to be done once.
1. sudo apt-get install git schroot debootstrap 1. SSH into the server as default.
2. git clone https://skia.googlesource.com/skia 2. sudo apt-get install git schroot debootstrap
3. Add the following to /etc/fstab and reboot: 3. git clone https://skia.googlesource.com/skia
4. cd ~/skia/experimental/webtry/setup
5. ./webtry_setup.sh
6. Add the following to /etc/fstab and reboot:
none /dev/shm tmpfs rw,nosuid,nodev,noexec 0 0 none /dev/shm tmpfs rw,nosuid,nodev,noexec 0 0
The above will allow ninja to run. See http://stackoverflow.com/questions/2009278/python-multiprocessing-permission-denied The above will allow ninja to run. See http://stackoverflow.com/questions/2009278/python-multiprocessing-permission-denied
4. Add the following to the /etc/schroot/minimal/fstab: 7. Add the following to the /etc/schroot/minimal/fstab:
/home/webtry/inout /inout none rw,bind 0 0 /home/webtry/inout /inout none rw,bind 0 0
5. Change /etc/monit/monitrc to: 8. Change /etc/monit/monitrc to:
set daemon 2 set daemon 2
@ -65,30 +71,30 @@ then run the following so it applies:
This means that monit will poll every two seconds that our application is up and running. This means that monit will poll every two seconds that our application is up and running.
6. Set the TCP keepalive. For more info see: 9. Set the TCP keepalive. For more info see:
https://developers.google.com/cloud-sql/docs/gce-access https://developers.google.com/cloud-sql/docs/gce-access
sudo bash -c 'echo 60 > /proc/sys/net/ipv4/tcp_keepalive_time' sudo bash -c 'echo 60 > /proc/sys/net/ipv4/tcp_keepalive_time'
Do the first time
-----------------
Do the following the first time you setup a machine, and each time you want to update the code running on the server
cd ~/skia/experimental/webtry/setup
./webtry_setup.sh
Once, after setup Once, after setup
----------------- =================
Do this step only once, but only after running webtry_setup.sh the first time Do this step only once, but only after running webtry_setup.sh the first time.
sudo debootstrap --variant=minbase wheezy /srv/chroot/webtry sudo debootstrap --variant=minbase wheezy /srv/chroot/webtry
To update the code
==================
1. SSH into the server as default.
2. cd ~/skia/experimental/webtry/setup
3. git pull
4. ./webtry_setup.sh
Third Party Code Third Party Code
---------------- ================
* res/js/polyfill.js - Various JS polyfill libraries. To rebuild or update * res/js/polyfill.js - Various JS polyfill libraries. To rebuild or update
see poly/README.md. see poly/README.md.