Add instructions for how to push a Mojo http handler to Google Compute.

Add instructions for how to push a Mojo http handler to Google Compute.

R=ben@chromium.org

Committed: https://chromium.googlesource.com/external/mojo/+/6c6ecb6df7e8a5974f165bf17736f0c567e49ba5

[jam, 2014-11-14 21:11:14]

Patchset #1 (id:1) has been deleted

[jam, 2014-11-14 21:11:21]

jam@chromium.org changed reviewers:
+ ben@chromium.org

[Ben Goodger (Google), 2014-11-15 05:32:46]

lgtm

[Ben Goodger (Google), 2014-11-15 05:34:07]

https://codereview.chromium.org/727023002/diff/20001/services/http_server/REA...
File services/http_server/README.md (right):

https://codereview.chromium.org/727023002/diff/20001/services/http_server/REA...
services/http_server/README.md:26: Now create a VM that'll run the binary. The
Debian image doesn't work because of some GLib dependencies in our binaries that
we should remove. Until then, you have to use the Ubuntu image:
are there bugs on these dependencies?

[jam, 2014-11-17 17:11:28]

https://codereview.chromium.org/727023002/diff/20001/services/http_server/REA...
File services/http_server/README.md (right):

https://codereview.chromium.org/727023002/diff/20001/services/http_server/REA...
services/http_server/README.md:26: Now create a VM that'll run the binary. The
Debian image doesn't work because of some GLib dependencies in our binaries that
we should remove. Until then, you have to use the Ubuntu image:
On 2014/11/15 05:34:07, Ben Goodger (Google) wrote:
> are there bugs on these dependencies?

just filed https://code.google.com/p/chromium/issues/detail?id=433886

[jam, 2014-11-17 17:54:31]

Committed patchset #3 (id:60001) manually as
6c6ecb6df7e8a5974f165bf17736f0c567e49ba5.