Jari Kolehmainen

Ok, so in my previous example there would be `db-loadbalancer` that belongs to both networks and app connects to database through that... sounds pretty good.

Should we move this to 1.5.0?

Currently it's not possible. We are going to refactor loadbalancer pretty soon to different codebase and that might bring us possibility to add support for multiple ports.

This might work (just an example): ``` lb: image: kontena/lb:latest ports: - "80:80" - "443:443" app-admin-proxy: image: kontena/haproxy:latest environment: - VIRTUAL_HOSTS=%{project}-app=admin.domain.com - BACKENDS=%{project}-app:8080 - KONTENA_LB_VIRTUAL_HOSTS=admin.domain.com - KONTENA_LB_INTERNAL_PORT=80 links: - lb...

@counterbeing I think it's possible to use one LB for multiple ports.. just remember that you need to include custom port (9000 in your case) in the `KONTENA_LB_VIRTUAL_HOSTS` env variable...

@morph027 > How far is that soon? ;) It's starting to happen: https://github.com/kontena/kontena-loadbalancer/pull/27

Agent should at least have time sync as health "source".

Unfortunately too late for 1.2.0.

> Is this still important given that clicking on an item now adds it to the hotbar (as long as it is connected). I presume this drag&drop would "Pin to...

@jim-docker I think the port forwarding is missing an environment variable that defines user configured HTTPS proxy (set via cluster settings).