Topics

FYI: GitLab Pages coming to their Community Edition - and it supports HTTPS


David A. Wheeler
 

FYI -

 

The GitLab Enterprise Edition has supported “GitLab Pages” (which serve static pages similar to GitHub pages).  Recently GitLab has announced that they’re adding “GitLab Pages” to their open source Community Edition.  Announcement here:

  https://about.gitlab.com/2016/12/24/were-bringing-gitlab-pages-to-community-edition/?

Details here:

  https://docs.gitlab.com/ee/pages/README.html

 

The good news is that it supports HTTPS, so this is yet another way that people can implement criterion https_sites.

 

There is a weird limitation: GitLab allows usernames and groupnames to have a dot, but if they do, they don’t work due to DNS interactions.  Obvious solution: New username/groupname.  Warning here:

https://docs.gitlab.com/ee/pages/README.html#limitations

 

GitLab’s “GitLab pages” mechanism directly support TLS with custom domains for projects – something that GitHub does not currently support.  Details here:

  https://docs.gitlab.com/ee/pages/README.html#add-a-custom-domain-to-your-pages-website

It’s not clear if GitLab will enable this mechanism in their Community edition – but it’d be great if they did.  If they don’t, I’m guessing that a CDN proxy would work in this case as well.

 

--- David A. Wheeler

 

 


Mark Rader
 

David

That's good news except for the dot problem. 

Mark


On Dec 24, 2016, at 1:45 PM, Wheeler, David A <dwheeler@...> wrote:

FYI -

 

The GitLab Enterprise Edition has supported “GitLab Pages” (which serve static pages similar to GitHub pages).  Recently GitLab has announced that they’re adding “GitLab Pages” to their open source Community Edition.  Announcement here:

  https://about.gitlab.com/2016/12/24/were-bringing-gitlab-pages-to-community-edition/?

Details here:

  https://docs.gitlab.com/ee/pages/README.html

 

The good news is that it supports HTTPS, so this is yet another way that people can implement criterion https_sites.

 

There is a weird limitation: GitLab allows usernames and groupnames to have a dot, but if they do, they don’t work due to DNS interactions.  Obvious solution: New username/groupname.  Warning here:

https://docs.gitlab.com/ee/pages/README.html#limitations

 

GitLab’s “GitLab pages” mechanism directly support TLS with custom domains for projects – something that GitHub does not currently support.  Details here:

  https://docs.gitlab.com/ee/pages/README.html#add-a-custom-domain-to-your-pages-website

It’s not clear if GitLab will enable this mechanism in their Community edition – but it’d be great if they did.  If they don’t, I’m guessing that a CDN proxy would work in this case as well.

 

--- David A. Wheeler

 

 

_______________________________________________
CII-badges mailing list
CII-badges@...
https://lists.coreinfrastructure.org/mailman/listinfo/cii-badges


David A. Wheeler
 

Mark Rader [mailto:msrader@gmail.com]:
That's good news except for the dot problem. 
I don't think the dot problem is a big deal. I suspect most people won't notice the limitation. For the few where it matters, just use another character. My GitHub *and* GitLab id is "david-a-wheeler" which works just fine.

Also: Note that GitLab was one of our early badge recipients. Their badge entry is here:
https://bestpractices.coreinfrastructure.org/projects/42

Here's the Hacker News discussion about this announcement:
https://news.ycombinator.com/item?id=13250203

--- David A. Wheeler