Bringing GitLab Pages to the Community Edition
about.gitlab.com
Bringing GitLab Pages to the Community Edition
1–10 of 29 posts
Re: Bringing GitLab Pages to the Community Edition
#2This also seems to be a direct result of GitHub's move to limiting GitHub Pages [1]
Good work, and keep it up GitLab Team! Lovely product, and well designed.
[1] - https://help.github.com/articles/what-is-github-pages/#usage...
Re: Bringing GitLab Pages to the Community Edition
#3I was looking for this feature a couple of days ago and saw it was in the EE. Which sucked for me and my tiny community- so I'm super pleased to hear this.
One of the things I'm not sure about though, is how does gitlab handle the domain per user? Do I delegate DNS to the gitlab instance itself or something?
Re: Bringing GitLab Pages to the Community Edition
#4This also seems to be a direct result of GitHub's move to limiting GitHub Pages [1] Good work, and keep it up GitLab Team! Lovely product, and well designed. [1] - https://help.github.com/articles/what-is-github-pages/#usage...
Thanks for your kind words!
EDIT: Job has commented in https://news.ycombinator.com/item?id=13250453
The announcement from GitHub might have triggered us. GitHub Pages was limited about 3 days go https://news.ycombinator.com/item?id=13227863
Job asked for votes 3 days ago https://gitlab.com/gitlab-org/gitlab-ce/issues/14605#note_20...
Looking at our internal chat logs it seems that the announcement got us thinking about pages again. But the decision to open source it was based on what kind of people used it (more small organizations than we thought, fewer large organizations than we thought).
I've asked Job to comment too.
BTW We're not sure if we'll limit GitLab.com Pages at some point, see "GitLab Pages with very high traffic (currently unlimited even in the free plan)" from https://about.gitlab.com/gitlab-com/#free-forever Of course you now always have the option to host your own.
Re: Bringing GitLab Pages to the Community Edition
#5I was looking for this feature a couple of days ago and saw it was in the EE. Which sucked for me and my tiny community- so I'm super pleased to hear this. One of the things I'm not sure about though, is how does gitlab handle the domain per user? Do I delegate DNS to the gitlab instance itself or something?
Glad to hear!
It depends a bit on what you want, but have a look in the documentation for details I couldn't give you by heart [0].
[0]: https://docs.gitlab.com/ee/pages/administration.html#setting...
Re: Bringing GitLab Pages to the Community Edition
#6I was looking for this feature a couple of days ago and saw it was in the EE. Which sucked for me and my tiny community- so I'm super pleased to hear this. One of the things I'm not sure about though, is how does gitlab handle the domain per user? Do I delegate DNS to the gitlab instance itself or something?
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-con...
BTW For instructions how to use your own domain see 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."
Re: Bringing GitLab Pages to the Community Edition
#7This also seems to be a direct result of GitHub's move to limiting GitHub Pages [1] Good work, and keep it up GitLab Team! Lovely product, and well designed. [1] - https://help.github.com/articles/what-is-github-pages/#usage...
The timing is coincidental, at least from my side.
We keep track of all mentions of GitLab on sources such as HN, but also Google+. There I was pointed to this comment [0]. This triggered me to look into the existing issue again [1] and reevaluate.
The data showed that there was no good reason for us to keep GitLab Pages in EE, so it made sense to move it to CE!
[0]: https://plus.google.com/u/1/115261498097261634859/posts/EWhA...
Re: Bringing GitLab Pages to the Community Edition
#8This also seems to be a direct result of GitHub's move to limiting GitHub Pages [1] Good work, and keep it up GitLab Team! Lovely product, and well designed. [1] - https://help.github.com/articles/what-is-github-pages/#usage...
The timing is coincidental, at least from my side. We keep track of all mentions of GitLab on sources such as HN, but also Google+. There I was pointed to this comment [0]. This triggered me to look into the existing issue again [1] and reevaluate. The data showed that there was no good reason for us to keep GitLab Pages in EE, so it made sense to move it to CE! [0]: https://plus.google.com/u/1/115261498097261634859/…
Cool! So the timing was a coincidence. Also see our internal chat log with timestamps https://gitlab.com/snippets/34152
Re: Bringing GitLab Pages to the Community Edition
#9Superb. Thank you, Sytse, and have a great holiday!
Re: Bringing GitLab Pages to the Community Edition
#10Superb. Thank you, Sytse, and have a great holiday!
Glad to hear you're happy! I don't want to take credit for this, it was mostly the wider community politely asking in https://gitlab.com/gitlab-org/gitlab-ce/issues/14605
We're thankful that the conversation was data driven and everyone assumed best intentions from each other. In the last few days we released 8.15 with auto deploy and web terminal https://about.gitlab.com/2016/12/22/gitlab-8-15-released/ and the company achieved its monthly, quarterly, and yearly sales goal. I can't think of a better way to celebrate and be amazed at what we did together in 2016.