The proposal to merge lp:~teknico/charms/precise/juju-gui/encrypt-api-env-connection into lp:~juju-gui/charms/precise/juju-gui/trunk has been updated.
Description changed to: Setup encrypted conn. to the API environment Pass the same certificate and private key used by nginx to the API environment, so that the websocket connection can use WSS. This sets the code up, but HTTPS is still disabled, and WSS too. To test this you need to enable HTTPS in config/nginx.conf.template, WSS in config/config.js.template, and expose the 443 port in hooks/start. Also, this is not yet working while deploying manually, and needs further testing. Do not land without checking first. https://codereview.appspot.com/7007045/ For more details, see: https://code.launchpad.net/~teknico/charms/precise/juju-gui/encrypt-api-env-connection/+merge/141107 -- https://code.launchpad.net/~teknico/charms/precise/juju-gui/encrypt-api-env-connection/+merge/141107 Your team Juju GUI Hackers is requested to review the proposed merge of lp:~teknico/charms/precise/juju-gui/encrypt-api-env-connection into lp:~juju-gui/charms/precise/juju-gui/trunk. -- Mailing list: https://launchpad.net/~yellow Post to : [email protected] Unsubscribe : https://launchpad.net/~yellow More help : https://help.launchpad.net/ListHelp
