2 ms·

Glad to hear we made the right decision. We open sourced it because we learned that small organizations were interested and your comment is another indication o

by sytse 10y ago

Glad to hear we made the right decision. We open sourced it because we learned that small organizations were interested and your comment is another indication of that. Regarding your question. I assume you're talking about a self hosted instance that offers a FQDN (not domain) in the form of username.yourgitlabhostname.com For documentation about this please see https://docs.gitlab.com/ee/pages/administration.html#dns-configuration https://docs.gitlab.com/ee/pages/administration.html#dns-con... BTW For instructions how to use your own domain see https://docs.gitlab.com/ee/pages/README.html https://docs.gitlab.com/ee/pages/README.html "As a last step, you need to configure your DNS and add a CNAME pointing to your user/group page. Click on the Details button of a domain for further instructions."

dwheeler 10y ago
This is great news! I lead the "CII Best Practices Badge" project for OSS projects - if you have an OSS project, and you meet certain requirements, you can get a badge. One criterion is that "The project sites (website, repository, and download URLs) MUST support HTTPS using TLS.": https://github.com/linuxfoundation/cii-best-practices-badge/blob/master/doc/criteria.md#sites_https https://github.com/linuxfoundation/cii-best-practices-badge/... I think making GitLab pages part of the community edition will make it easier to meet this criterion. Congrats, and thanks!
- sytse 10y ago
  Cool, I didn't consider that use case but it makes a lot of sense. BTW I love the CII Best Practices project and GitLab is proudly wearing the badge on https://gitlab.com/gitlab-org/gitlab-ce/#gitlab https://gitlab.com/gitlab-org/gitlab-ce/#gitlab