Re:Gitlab More Than Doubles Valuation to $2.75B Ahead of Pla...
by mcintyre1994 on Tuesday September 17, 2019 @05:52PM
(#21000469)
Thanks for the response! Reading through their docs it looks really nicely integrated with all the CI stuff there, a good example of them taking advantage of all the flexibility and power that has. Nice!
Re:Gitlab More Than Doubles Valuation to $2.75B Ahead of Pla...
by frenchyatwork on Tuesday September 17, 2019 @01:10PM
(#20997536)
> automatic LetsEncrypt renewal for custom domains
Really, is this new? I wasn't aware of it.
Re:Gitlab More Than Doubles Valuation to $2.75B Ahead of Pla...
by Already__Taken on Tuesday September 17, 2019 @03:32PM
(#20999164)
I want to say this is about 6/mo new guessing from when I wanted it to when I realised it had been added.
Re:Gitlab More Than Doubles Valuation to $2.75B Ahead of Pla...
by frenchyatwork on Wednesday September 18, 2019 @03:56PM
(#21009373)
Oh, I was thinking of letsencrypt support directly in gitlab pages.
Re:Gitlab More Than Doubles Valuation to $2.75B Ahead of Pla...
by Already__Taken on Wednesday September 18, 2019 @06:28PM
(#21011055)
No you're correct, gitlab pages now does that. I was trying to do it with CI jobs but now it's native.
Github's is tightly coupled to Jekyll, and—more specifically—to this single Gem https://github.com/github/pages-gem Also, this might have changed, but last time I interacted with it, it lacked any real control over your source repo structure: there's some arcane rules about either giving it a certain name under a certain GH org, or using a specifically named branch (`gh-pages`).
Github were also pretty lax about adding HTTPS support to custom domains their Pages service.
In comparison, GL pages allows:
- using any SSG[0]
- writing your own custom SSG (even integrated/including in your repo itself)
- automatic LetsEncrypt renewal for custom domains
- out-of-repo secrets management for any tasks within your SSG build/deploy steps
[0] https://about.gitlab.com/2016/06/17/ssg-overview-gitlab-page...