determine app name automatically

[afeld]

This is purely for convenience.

With the way cloud.gov is set up (and maybe all Cloud Foundry deployments?), it doesn't really matter which app the tunneling goes through, except for (maybe) a small amount of overhead. We should just grab the first available app in the space and use that.

[afeld]

An alternative is pushing a dedicated (small) app for the tunneling, to reduce the likelihood that the app is messed with while the user is tunneling through it. I assume (but have not verified) that this would break cf ssh.

[mogul]

You might in future need to pick/push an app that explicitly has a binding to the service in question... Future versions of Cloud Foundry may do a lot more internal pinhole firewalling based on bindings.

[afeld]

We could make it optional...? Or just leave it as is. Not that big of an inconvenience.

[afeld]

Conduit's approach is to push a small static app that is used for the tunneling, then bind the service(s) to it.