step by step for gitlab with the ssl-termination-proxy

[Merlijn Sebrechts]

Zeppelin is a tricky one, because it also uses websockets on top of normal
http. I don't want to use the `http` interface for this because support for
this wouldn't be backwards compatible; Zeppelin will not work behind the
current HAProxy Charm. More info on how to proxy zeppelin with nginx
<https://zeppelin.apache.org/docs/0.7.0/security/authentication.html>.

So do we create a new interface that combines both `http` and `websockets`
or do we use two interfaces?

2017-04-28 15:14 GMT+02:00 Rick Harding <rick.harding at canonical.com>:

> In the Juju Show episode this week [1] I mentioned that I was tinkering
> with getting Gitlab testing. There was one tweak that needed doing so that
> you can get Gitlab to work with it being proxied. You have to configure its
> "external_url" config setting and then reconfigure Gitlab.
>
> I've walked through the step by step in my blog post here:
> http://mitechie.com/blog/2017/4/27/giving-gitlab-an-afternoon-spin\
>
> I want to thank Tom for responding to my poking around his Gitlab charm
> and for the awesome stuff i the ssl-termination-proxy charm from the Tengu
> folks. It's a really nice combo [2] and I'll follow up on that awesomeness
> in a bit.
>
> 1: https://www.youtube.com/watch?v=h2X9gIxXPH8&t=2s
> 2: https://jujucharms.com/u/spiculecharms/gitlab-ssl
>
> Rick
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20170428/37d06f42/attachment.html>