Skip to Content

project pages -- case study in GitLab

1 Beginning

Prof Lu asks me to to build a GitHub pages using custom domain. So I explore whether GitHub project pages can use custom domain.

I guess since the pages of repo project lives in, it seems incompatible with CNAME record, which points one (sub)domain to another (sub)domain, i.e., the /project part is not allowed).

But GitHub crashes since about 11:30 (Beijing time), after a lot of depression, I decide to try on GitLab.

2 Curve to GitLab

The results quite surprised me. It turns out that for custom domain of project pages is also, the same as that of user pages 1.

For example:

repo url custom domain

Then I can’t hesitate to ask a question: what if I create DBA/index.html in repo?

3 Back to GitHub

In the evening, I can normally use GitHub, but the build for Pages pends. I had no option but to create demo files and wait for result. Finally GitHub Pages recovers in the next day.

It turns out the case for GitHub is nearly identical to that of GitLab. Except that after you enable custom domain, would automatically jumps 2 to . Thus we lose the chance to ask the above question for GitHub.

  1. as a special rule, GitLab asks you to also set TXT record for verifying your DNS↩︎

  2. to be precise, this only happens after you enforce HTTPS↩︎