Closed timhughes closed 9 years ago
+1 and for some context on why: gitlab ci runners with buggy ssl support or out-of-date CA bundles.
Actually, this doesn't look like a puppet-gitlab issue but an issue with how the gitlab::nginx chef recipe interprets the url.
@erik-stephens see the pull request. In nutshell, if you dont "redirect_http_to_https" then you dont deploy ssl certs.
My use case is that I run apache on port 80 so I set "redirect_http_to_https = False" (or dont set it at all) so that nginx doesn't listen on port 80. This causes the erb template to not include ssl certificates. My merge #127 request fixes the logic around this and also includes tests that cover what I believe the logic should be.
@timhughes Looks good to me. Not sure what I was linking to.
Module transitioned to here: https://github.com/vshn/puppet-gitlab
This should probably be dependent on the
external_url
parameter starting withhttps