charm, allow binding to just 443 so can colocate with webapp on port 80

Bug #1256426 reported by Kapil Thangavelu
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-gui
Fix Released
High
Jeff Pihach

Bug Description

gui binds also to 80 for redirect afaicr, would be nice to make that configurable.

Revision history for this message
Richard Harding (rharding) wrote :

Moving to the gui charm.

Changed in juju-gui:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Jeff Pihach (hatch) wrote :

This is especially attractive when wanting to deploy an entire bundle stack to a single machine.

Currently the GUI automatically redirects requests to port 80 to port 443 when secure=true. If we allowed the user to set a new https port we would also want to stop binding 80 at that point as well.

Revision history for this message
Stephen Nuchia (snuchia) wrote :

I just hit this. To conserve my allocation of cloud money I wanted to keep all the long-lived services on one small instance. Tried installing the juju gui and puppet master to machine 0. Neither charm supports a "port" setting so kaboom. So, +1. It shouldn't be all that hard to expose a port number, right?

Revision history for this message
Richard Harding (rharding) wrote :

Stephen, definitely. I'll move this up to one of the maintenance tasks we look at this next two weeks here. Thanks for +1'ing it.

Jeff Pihach (hatch)
Changed in juju-gui:
assignee: nobody → Jeff Pihach (hatch)
Jeff Pihach (hatch)
Changed in juju-gui:
status: Triaged → In Progress
Changed in juju-gui:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.