Why it is so cool that GitLab Pages becomes a part of CE(free & open source)?
What is GitLab Pages, and what you can do with it: - Example: Personal website
Actually Pages is more than just Pages. It is about publishing.
- TODO: find related issue.
What can you use it for:
-
as a staging website
-
to host real websites
-
reports generation and hosting
-
spelling and style validation
-
Before: At GitLab.com - for free. Or you buy a license and host it on your own server.
-
After: At GitLab.com - for free. On your instance of GitLab CE.
Who benefits from it:
- non-commercial organizations
- regular developers, for personal usage
- commercial usage (find a use case where a guy used GitLab Pages to build & host hundreds of client's websites)
How the decision was made:
- how we decide what goes to EE, what to CE
- we thought that it'll be more relevant to big organizations
- it turned out that we were wrong(discussion in the epic "Make GitLab Pages free" issue)
Can GitLab randomly move features between CE and EE?
- Nope. We never moved a single issue from CE to EE, and not going to make this happen. (Find a link in HN discussion thread, + link to page on handbook)
How to set it up (https://news.ycombinator.com/item?id=13250444)
- Installing GitLab
- DNS configuration
- Custom domains
- TLS (example: https://gitlab.com/pages/pages.gitlab.io/issues/29#note_20349421)
- example pipeline
- examples for different technologies