Fix probe connected status

[foot]

fixes #255

[foot]

@davkal RFR

[davkal]

Code looks good. Still need to see it in action. Is it deployed to dev?

[foot]

Nope, you can test it w/ the BACKEND_HOST trick:

$ BACKEND_HOST=frontend.dev.weave.works npm start

You can add probes to dev.weave.works by applying this to scope

diff --git a/docker/entrypoint.sh b/docker/entrypoint.sh
index b38721d..7f1fea6 100755
--- a/docker/entrypoint.sh
+++ b/docker/entrypoint.sh
@@ -108,7 +108,7 @@ while true; do
                 shift
             fi
             PROBE_ARGS="$PROBE_ARGS -token=$ARG_VALUE"
-            echo "scope.weave.works:80" >/etc/weave/apps
+            echo "frontend.dev.weave.works:80" >/etc/weave/apps
             touch /etc/service/app/down
             ;;
         --no-app)

and running

make && ./scope stop && ./scope launch

ORRR.... we could deploy this branch to dev? :)

[foot]

weaveworks/scope#777 suggests you shouldn't have to apply that diff and that you can just start w/

$ scope launch --service-token=abc frontend.dev.weave.works:80 # for dev

[foot]

But the scope ws:// is not getting correctly connected up w/ the BACKEND_PROXY hack right now... not sure if thats possible, having a quick look..

[davkal]

the code looks good. @2opremio would it be ok if you test it on your next deploy to dev?

[davkal]

Just tried to test this, but running into the JS error from #285 . Need to merge #284 asap

[davkal]

LGTM!!