Set up an stunnel endpoint for the engine.

blimp/engine/start_engine.sh

Index: blimp/engine/start_engine.sh
diff --git a/blimp/engine/start_engine.sh b/blimp/engine/start_engine.sh
new file mode 100755
index 0000000000000000000000000000000000000000..c1c6bab60b4d0c0f9d14312f761c5d09c802b345
--- /dev/null
+++ b/blimp/engine/start_engine.sh
@@ -0,0 +1,12 @@
+#!/bin/bash
+
+# Copyright 2016 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+stunnel -p /engine/data/stunnel.pem -P /engine/stunnel.pid -d 25467 -r 12345

[maniscalco, 2016/01/27 17:02:10]

What happens when stunnel fails?  Will this script (and the container) be
terminated?  Seems like we'd want the script to terminate if either stunnel or
the engine terminate.  That way the higher level will restart the container.

[marcinjb, 2016/01/28 19:29:45]

Done.

+exec /engine/blimp_engine_app \

[maniscalco, 2016/01/27 17:02:10]

One of the feature we're losing with this change is the ability to pass
arbitrary arguments to the engine when running the container from the command
line.  Maybe we should make start_engine.sh a more full-featured script and have
it pass some/all of its args to blimp_engine_app.  Let's chat about this more in
person.

[marcinjb, 2016/01/28 19:29:45]

Done.

+  --disable-gpu \
+  --use-remote-compositing \
+  --disable-cached-picture-raster \
+  --blimp-client-token-path=/engine/data/client_token