March 2023
M	T	W	T	F	S	S
	1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31

Archive for the ‘HTTPS/TLS security’ Category

HTTPS Is Actually Everywhere | Electronic Frontier Foundation (so HTTPS everywhere will sunset January 2023)

Posted by jpluimers on 2022/07/08

I missed this announcement: [Wayback/Archive] HTTPS Is Actually Everywhere | Electronic Frontier Foundation.

Though in practice there still are a few sites not having HTTPS (usually old blogs, sometimes old forums too), almost all have (thanks Let’s Encrypt!) and many not even support HTTP any more.

So the HTTPS Extension in Google Chrome recently pointed me to [Wayback/Archive] Set Up HTTPS by Default in Your Browser | Electronic Frontier Foundation, which pointed me to the above post, which taugt me that most browsers (Firefox, Chrome, Edge and Safari) by now have an HTTPS-only mode which you can enable by hand or sometimes is just the only way.

Cool, I love progress!

–jeroen

Posted in Encryption, HTTPS/TLS security, Let's Encrypt (letsencrypt/certbot), Power User, Security | Leave a Comment »

Setting up a GitLab project so it is served over https as a gitlab.io and a custom subdomain

Posted by jpluimers on 2022/05/05

Last week, I posted about Setting up a GitHub project so it is served over https as a custom github.io subdomain.

Today it’s the equivalent, but on GitLab.

Why GitLab? Two major reasons: unlike GitHub:

it’s open source
provides way more granular control over permissions
allows a hierarchy of repositories on which you can specify that permission control

Already 2. and 3. combined are a huge advantage, though we will see that 3. also makes some of the subcases (hosting as user.gitlab.io from account gitlab.com/user where user is your username) is harder than the similar user.github.io, github.com/user combo.

So here we go, starting with a similar set of links:

The goal is to have

page projects as or under wiert.gitlab.io (like wiert.gitlab.io/wiert)
a gitlabstatus.wiert.me plain html (or maybe markdown) page project that eventually will show some status information (kind of like status.gitlab.com, but for different things).

The beauty of GitLab is that it supports hierarchies of repositories through groups and subgroups, so I already had these subgroups hoping they would cover both the first and second kind of page projects:

Steps I did

Since there are quite a few links above, here are the steps I took from my gitlab.com/wiert account and gitlab.com/wiert.me group.

Steps for wiert.gitlab.io/wiert

For wiert.gitlab.io/wiert, try A (failed in part, and therefore interesting to understand why):
1. Under leaf group gitlab.com/wiert.me/public/web/sites/gitlab.io, created a new GitLab repository
2. Chose “Create from template”
3. Chose the template “Pages/Plain HTML”
4. Named the project “wiert” (with slug “wiert“) so it would appear at gitlab.com/wiert.me/public/web/sites/gitlab.io/wiert
5. From the left sidebar, navigated to your project’s “CI/CD”, then “Pipelines”
6. Now I got in a confusing situation as the page indicated “There are currently no pipelines.”, but an enabled blue “Run pipeline” button:
  
  By default there is no CI/CD pipeline, but there is an enabled blue “Run pipeline” button: confusing.
7. Clicked the “Run pipeline” button nonetheless, and that created [Wayback/Archive.is] a pipeline asking for parameters (that already had correct default values) and revealed a new blue “Run pipeline” button.
8. Clicked that new “Run pipeline button” which created [Wayback/Archive.is] a job and deployed the page.
9. From the left sidebar, navigated to “Settings”, then “Pages” to get the links to the pages site: http://wiert.me.gitlab.io/public/web/sites/gitlab.io/wiert/ and https://wiert.me.gitlab.io/public/web/sites/gitlab.io/wiert/
  
  Warning: When using Pages under the general domain of a GitLab instance (gitlab.io), you cannot use HTTPS with sub-subdomains.
  
  The sites do work (see the [Archive.is http version] and [Archive.is https version]), but the HTTPS fails because wiert.me.gitlab.io does not match the SANs (Subject Alternative Names) in the certificate: *.gitlab.io, gitlab.io
For wiert.gitlab.io/wiert, try B (failed, and therefore interesting to understand why):
1. In my my groups gitlab.com/dashboard/groups, added a new group wiert
2. Added subgroups until the leaf gitlab.com/wiert/public/web/sites/gitlab.io which as URL is gitlab.com/wier1/public/web/sites/gitlab.io because user account wiert already occupies gitlab.com/wiert.
3. Under leaf group gitlab.com/wier1/public/web/sites/gitlab.io, created a new GitLab repository
4. Chose “Create from template”
5. Chose the template “Pages/Plain HTML”
6. Named the project “wiert” (with slug “wiert“) so it would appear at gitlab.com/wiert.me/public/web/sites/gitlab.io/wiert
7. From the left sidebar, navigated to your project’s “CI/CD”, then “Pipelines”
8. Again there was “There are currently no pipelines.”, but an enabled blue “Run pipeline” button, which I clicked
9. That created [Wayback/Archive.is] a pipeline asking for parameters (that already had correct default values) and revealed a new blue “Run pipeline” button.
10. Clicked that new “Run pipeline button” which created [Wayback/Archive.is] a job deployed the page.
11. From the left sidebar, navigated to “Settings”, then “Pages” to get the links to the pages site: http://wier1.gitlab.io/public/web/sites/gitlab.io/wiert and https://wier1.gitlab.io/public/web/sites/gitlab.io/wiert.
  Bummer: again not the wiert.gitlab.io/wiert I hoped for
  The sites do work (see the [Archive.is http version] and [Archive.is https version]). The HTTP does not redirect to the HTTP version, as I did not tick the
  
  ☐ Force HTTPS (requires valid certificates)
12. If a user wiert exists and occupies gitlab.com/wiert, then a group named wiert cannot occupy gitlab.com/wiert, and therefore a project named wiert within that group won’t be deployed to wiert.gitlab.io/wiert.
  Maybe this can be shortened like “if there is a user wiert, then no group named wiert cannot be used to contain a project named wiert to host as wiert.gitlab.io/wiert“.
  Let’s find out!
For wiert.gitlab.io/wiert, try C (success, steps 1, 3, 4, 7 and 8 were the key ones):
1. In my user gitlab.com/wiert, created a new GitLab repository
2. Chose “Create from template”
3. Chose the template “Pages/Plain HTML”
4. Named the project “wiert” (with slug “wiert“) so it would appear at gitlab.com/wiert
5. The odd but cool thing is that the actual project now ended up at gitlab.com/wiert/wiert:
6. From the left sidebar, navigated to your project’s “CI/CD”, then “Pipelines”
7. Again there was “There are currently no pipelines.”, but an enabled blue “Run pipeline” button, which I clicked
8. That created [Wayback/Archive.is] a pipeline asking for parameters (that already had correct default values) and revealed a new blue “Run pipeline” button.
9. Clicked that new “Run pipeline button” which created [Wayback/Archive.is] a job deployed the page.
10. From the left sidebar, navigated to “Settings”, then “Pages” to get the links to the pages site: http://wiert.gitlab.io/wiert/ and https://wiert.gitlab.io/wiert/.
  Success: finally the wiert.gitlab.io/wiert I hoped for:
  
  Success: published at https://wiert.gitlab.io/wiert/
  
  The sites do work fine (see the [Archive.is http version] and [Archive.is https version]). The HTTP does not redirect to the HTTP version, as I did not tick the
  
  ☐ Force HTTPS (requires valid certificates)

Steps for wiert.gitlab.io

For wiert.gitlab.io, try A (failed, and therefore interesting to understand why):
1. Under leaf group gitlab.com/wiert.me/public/web/sites/gitlab.io, created a new GitLab repository
2. Chose “Create from template”
3. Chose the template “Pages/Plain HTML”
4. Named the project “wiert.gitlab.io” (with slug “wiert.gitlab.io“) so it would appear at gitlab.com/wiert.me/public/web/sites/gitlab.io/wiert.gitlab.io
5. From the left sidebar, navigated to your project’s “CI/CD”, then “Pipelines”
6. Again there was “There are currently no pipelines.”, but an enabled blue “Run pipeline” button, which I clicked
7. That created [Wayback/Archive.is] a pipeline asking for parameters (that already had correct default values) and revealed a new blue “Run pipeline” button.
8. Clicked that new “Run pipeline button” which created [Wayback/Archive.is] a job deployed the page.
9. From the left sidebar, navigated to “Settings”, then “Pages” to get the links to the pages site: http://wiert.me.gitlab.io/public/web/sites/gitlab.io/wiert.gitlab.io and https://wiert.me.gitlab.io/public/web/sites/gitlab.io/wiert.gitlab.io.
  Failure: not the wiert.gitlab.io I hoped for.
  
  The sites do work (see the [Archive.is http version] and [Archive.is https version]), but the HTTPS fails because wiert.me.gitlab.io does not match the SANs (Subject Alternative Names) in the certificate: *.gitlab.io, gitlab.io. The HTTP does not redirect to the HTTP version, as I did not tick the
  
  ☐ Force HTTPS (requires valid certificates)
For wiert.gitlab.io, try B (failed, and therefore interesting to understand why):
1. Under leaf group gitlab.com/wier1/public/web/sites/gitlab.io, created a new GitLab repository
2. Chose “Create from template”
3. Chose the template “Pages/Plain HTML”
4. Named the project “wiert.gitlab.io” (with slug “wiert.gitlab.io“) so it would appear at gitlab.com/wier1/public/web/sites/gitlab.io/wiert.gitlab.io
5. From the left sidebar, navigated to your project’s “CI/CD”, then “Pipelines”
6. Again there was “There are currently no pipelines.”, but an enabled blue “Run pipeline” button, which I clicked
7. That created [Wayback/Archive.is] a pipeline asking for parameters (that already had correct default values) and revealed a new blue “Run pipeline” button.
8. Clicked that new “Run pipeline button” which created [Wayback/Archive.is] a job deployed the page.
9. From the left sidebar, navigated to “Settings”, then “Pages” to get the links to the pages site: http://wier1.gitlab.io/public/web/sites/gitlab.io/wiert.gitlab.io and https://wier1.gitlab.io/public/web/sites/gitlab.io/wiert.
  Bummer: again not the wiert.gitlab.io I hoped for
  The sites do work (see the [Archive.is http version] and [Archive.is https version]). The HTTP does not redirect to the HTTP version, as I did not tick the
  
  ☐ Force HTTPS (requires valid certificates)
10. Try A and B were almost identical to wiert.gitlab.io/wiert try A and B, so let’s see if the solution C for that also works for us:
For wiert.gitlab.io, try C (success, steps 1, 3, 4, 7 and 9 were the key ones)
1. In my user gitlab.com/wiert, created a new GitLab repository
2. Chose “Create from template”
3. Chose the template “Pages/Plain HTML”
4. Named the project “wiert.gitlab.io” (with slug “wiert.gitlab.io“) so it would appear at gitlab.com/wiert/wiert.gitlab.io.
5. From the left sidebar, navigated to your project’s “CI/CD”, then “Pipelines”
6. Again there was “There are currently no pipelines.”, but an enabled blue “Run pipeline” button, which I clicked
7. That created [Wayback/Archive.is] a pipeline asking for parameters (that already had correct default values) and revealed a new blue “Run pipeline” button.
8. Clicked that new “Run pipeline button” which created [Wayback/Archive.is] a job deployed the page.
9. From the left sidebar, navigated to “Settings”, then “Pages” to get the links to the pages site: http://wiert.gitlab.io/ and https://wiert.gitlab.io/.
  Success: finally the wiert.gitlab.io I hoped for with working sites (see the [Archive.is http version] and [Archive.is https version]).
10. Note the HTTP does not redirect to the HTTP version, as I did not tick the
  
  ☐ Force HTTPS (requires valid certificates)

Steps for gitlabstatus.wiert.me

Having learned from the GitHub githubstatus.wiert.me procedure (where I had to wait a long time for the default *.wiert.me domain mapping timeout and the githubstatus.wiert.me DNS CNAME record to become effective), I started on the DNS CNAME record side which is documented at [Wayback] Custom domains and SSL/TLS certificates: Section 3. Set up DNS records for Pages: For subdomains | GitLab:

Subdomains (subdomain.example.com) require:

A DNS CNAME record pointing your subdomain to the Pages server.

A DNS TXT record to verify your domain’s ownership.

From DNS Record To

subdomain.example.com CNAME namespace.gitlab.io

_gitlab-pages-verification-code.subdomain.example.com TXT gitlab-pages-verification-code=00112233445566778899aabbccddeeff

Note that, whether it’s a user or a project website, the CNAME should point to your Pages domain (namespace.gitlab.io), without any /project-name.

From	DNS Record	To
`subdomain.example.com`	`CNAME`	`namespace.gitlab.io`
`_gitlab-pages-verification-code.subdomain.example.com`	`TXT`	`gitlab-pages-verification-code=00112233445566778899aabbccddeeff`

The value for the TXT record is only known after you created the pages project, but the value for the CNAME record is known beforehand:

From DNS Record To

gitlabstatus.wiert.me CNAME namespace.gitlab.io

From	DNS Record	To
`gitlabstatus.wiert.me`	`CNAME`	`namespace.gitlab.io`

So let’s see if I can do this in one try, with these steps:

For gitlabstatus.wiert.me, try A (success, steps 1, 3, 4, 7 and 9 were the key ones)
1. In my DNS settings of the wiert.me domain, created a CNAME record from gitlabstatus.wiert.me to namespace.gitlab.io:
  gitlabstatus.wiert.me CNAME record pointing to namespace.gitlab.io
2. Under leaf group gitlab.com/wiert.me/public/web/sites/wiert.me, created a new GitLab repository
3. Chose “Create from template”
4. Chose the template “Pages/Plain HTML”
5. Named the project “gitlabstatus.wiert.me” (with slug “gitlabstatus.wiert.me“) so it would appear at gitlab.com/wiert.me/public/web/sites/wiert.me/gitlabstatus.wiert.me
6. From the left sidebar, navigated to your project’s “CI/CD”, then “Pipelines”
7. Again there was “There are currently no pipelines.”, but an enabled blue “Run pipeline” button, which I clicked
8. That created [Wayback/Archive.is] a pipeline asking for parameters (that already had correct default values) and revealed a new blue “Run pipeline” button.
9. Clicked that new “Run pipeline button” which created [Wayback/Archive.is] a job deployed the page.
10. From the left sidebar, navigated to “Settings”, then “Pages” to get the links to the pages site: http://wiert.me.gitlab.io/public/web/sites/wiert.me/gitlabstatus.wiert.me and https://wiert.me.gitlab.io/public/web/sites/wiert.me/gitlabstatus.wiert.me.
  Intermediate success: working sites (see the [Archive.is http version] and [Archive.is https version]).
11. Now it is time to get the DNS CNAME record from gitlabstatus.wiert.me to namespace.gitlab.io into operation by clicking the “New Domain” button:
  
  “New Domain” button in the “Pages” settings.
12. There I filled in the correct gitlabstatus.wiert.me domain name, then pressed the “Create New Domain” button:
  
  New domain becomes gitlabstatus.wiert.me
13. Then a page appeared voiding the DNS CNAME work I already did: the documentation is clearly wrong as these are the two DNS record entries to be made as shown by gitlab.com/wiert.me/public/web/sites/wiert.me/gitlabstatus.wiert.me/pages/domains/gitlabstatus.wiert.me:
  
  Correct instructions for the DNS records to get gitlabstatus.wiert.me working
  
  Subdomains (gitlabstatus.wiert.me) require:
  - A DNS CNAME record pointing your subdomain to the Pages server.
  - A DNS TXT record to verify your domain’s ownership.
  From DNS Record To
  
  gitlabstatus.wiert.me CNAME wiert.me.gitlab.io.
  
  _gitlab-pages-verification-code.gitlabstatus.wiert.me TXT gitlab-pages-verification-code=c5619988d386b1a36c253ce05db55dbb
  Basically the whole namespace.gitlab.io part of the documentation is a placeholder for the actual namespace that belongs to the leaf group the pages project is in (in my case wiert.me).
  
  So this is the new DNS entry, for which I had to wait until the DNS TTL to time out and effectuate:
  
  New DNS gitlabstatus.wiert.me CNAME record pointing to wiert.me.gitlab.io
  
  Note that this DNS administrative interface from WordPress.com does omit the final period of the CNAME destination (officially this would be wiert.me.gitlab.io.)
14. After the CNAME DNS record, I also made the TXT DNS record:
  
  New DNS TXT record for verification of gitlabstatus.wiert.me
  
  Then I waited a little for the DNS TXT record to be saved and try the verification of the TXT record.
15. Even then, verification took some time. I had to click the refresh button a few times before verification succeeded:
  
  The DNS TXT record for gitlabstatus.wiert.me finally got verified
16. Now I could press blue “Save Changes” button below and waited for the CNAME record DNS TTL to expire so I could check the domain and – hopefully – the TLS certificate to be requested by Let’s Encrypt:
  
  After the gitlabstatus.wiert DNS TXT record got verified, I could save the domain information
17. After the old CNAME record DNS TTL expired and the new CNAME record came into effect, the domain became available as http://gitlabstatus.wiert.me/:
  
  Waiting for gitlabstatus.wiert.me to become active
18. After verification, the “Domains (1)” bit changed from this:
  
  Domain gitlabstatus.wiert.me information before verification
  
  to this:
  
  Domain gitlabstatus.wiert.me information after verification
19. In the mean time, also the TLS certificate got issued by Let’s Encrypt, so the final sites now both worked: http://gitlabstatus.wiert.me/ and https://gitlabstatus.wiert.me/.
20. Success: finally the gitlabstatus.wiert.me I hoped for with working sites (see the [Archive.is http version] and [Archive.is https version] for the wiert.me domain, and [Archive.is http version] and [Archive.is https version] for the wiert.me domain).
21. Note the HTTP does not redirect to the HTTP version, as I did not tick the
  
  ☐ Force HTTPS (requires valid certificates)

From	DNS Record	To
`gitlabstatus.wiert.me`	`CNAME`	`wiert.me.gitlab.io.`
`_gitlab-pages-verification-code.gitlabstatus.wiert.me`	`TXT`	`gitlab-pages-verification-code=c5619988d386b1a36c253ce05db55dbb`

In retrospect, this could have been shorter when I had done the DNS part later, which is contrary to how to do this with GitHub.

Conclusion

The conclusion seems this:

Gitlab Page repositories to be published as or under wiert.gitlab.io need to reside directly under user wiert. Having them reside under a different group like wiert or wiert.me won’t work.

Or in more generic terms:

When creating pages as user.gitlab.io you have to put your pages projects directly under your user account gitlab.com/user.

Putting them under groups or leaf groups fails, no matter if the (leaf) group is named user or otherwise.

In addition, you can add custom domains to any Gitlab repository (even one that never stated out as a GitLab Pages repository). It will work as soon as the domain DNS mapping is setup through both a CNAME mapping record and TXT verification record.

The steps for this in your GitLab repository are:

Ensure you have a valid .gitlab-ci.yml file at the root of your repository; I used the [Wayback/Archive.is] one from [Wayback/Archive] GitLab Pages examples / plain-html · GitLab as my site is purely static
Ensure you have a valid index.html file in the public directory of your repository, similar to [Wayback/Archive] GitLab Pages examples / plain-html · GitLab
When both 1. and 2. are committed in your repository at GitLab, then it will automatically be deployed to a docker container on gitlab.io, which allows the outside world to visit your GitHub Pages sie, and the Let’s Encrypt Certificate to be generated (and prevents this error: [Wayback/Archive] GitLab Pages integration with Let’s Encrypt | GitLab: “Something went wrong while obtaining the Let’s Encrypt certificate”).
Under “Settings” -> “Pages”, add a new domain name to the repository: now it automatically becomes a GitLab Pages repository.
When adding the domain, the settings page will show both a DNS CNAME record and DNS TXT record; ensure both are applied on your primary DNS name server and replicated to all authoritative DNS name servers.
Save the new page.
Check if the page is available on the new domain you added.
Optionally under “Settings” -> “Pages” enable the “Force HTTPS (requires valid certificates)” option and save.

TLS information

Note: I saved the TLS information – including certificates here:

[Wayback] certcheckerapp.com/home?hostname=wiert.me.gitlab.io&hideResult=false
- [Wayback] Wildcard GitLab certificate with serial number 5B0C885BD0E0A1A52AD5C29D for *.gitlab.io, gitlab.io.
- [Wayback] Certificate chain
[Wayback] certcheckerapp.com/home?hostname=wier1.gitlab.io&hideResult=false
- [Wayback] Wildcard GitLab certificate with serial number 5B0C885BD0E0A1A52AD5C29D for *.gitlab.io, gitlab.io.
- [Wayback] Certificate chain
[Wayback] certcheckerapp.com/home?hostname=wiert.gitlab.io&hideResult=false
- [Wayback/Archive.is] Wildcard GitLab certificate with serial number 5B0C885BD0E0A1A52AD5C29D for *.gitlab.io, gitlab.io.
- [Wayback] Certificate chain
[Wayback] certcheckerapp.com/home?hostname=gitlabstatus.wiert.me&hideResult=false
- [Wayback/Archive.is] Regular domain certificate with serial number 3380904328FD4633E6CF27FE9B7D5BE25AE for gitlabstatus.wiert.me.
- [Wayback/Archive.is] Let’s Encrypt issuer certificate with serial number 912B084ACF0C18A753F6D62E25A75F5A for R3.
- [Wayback/Archive.is] X1 root certificate with serial number 4001772137D4E942B8EE76AA3C640AB7 for ISRG Root X1.
- [Wayback] Certificate chain

More about the Let’s Encrypt certificates at [Wayback] Chain of Trust – Let’s Encrypt:

–jeroen

Read the rest of this entry »

Posted in Cloud, Communications Development, Development, DNS, Encryption, GitLab, Hosting, HTML, HTTPS/TLS security, Infrastructure, Internet, Internet protocol suite, Let's Encrypt (letsencrypt/certbot), Power User, Software Development, Source Code Management, TCP, TLS, Web Development | Leave a Comment »

capitaltg/thea: Certificate Checker and https://certchecker.app site

Posted by jpluimers on 2022/05/03

[Wayback/Archive.is] capitaltg/thea: Certificate Checker

Certificate Checker provides an easy-to-use solution to check certificates, certificate chains, and TLS configurations. To run Certificate Checker for publicly-accessible web sites you can go to: https://certchecker.app and enter in there a URL to check.

Users can easily run Certificate Checker in an internal network to validate or troubleshoot their TLS configuration. To run it on a local network you can run the Docker image as described below. You can also build the application and deploy it on an existing server.

It runs on [Wayback/Archive.is] Certificate Checker.

I used it to check various certificates and chains, including those for my GitHub Pages explained last week in Setting up a GitHub project so it is served over https as a custom subdomain.

–jeroen

Posted in Communications Development, Development, Encryption, HTTPS/TLS security, Internet protocol suite, Let's Encrypt (letsencrypt/certbot), Power User, Security, Software Development, TCP, TLS, Web Development | Leave a Comment »

Setting up a GitHub project so it is served over https as a github.io and a custom subdomain

Posted by jpluimers on 2022/04/27

Some links that helped me getting this working:

2018: [Wayback] How to use lets Encrypt SSL with github pages with custom subdomain | by Hojjat Ali Mohammadi | Medium
2018: [Wayback/Archive.is] Setting up GH-pages with custom domain, strict (end-to-end) SSL with CloudFlare DNS & CDN
2018: [Wayback] Custom domains on GitHub Pages gain support for HTTPS | The GitHub Blog
2016: [Wayback] HTTPS for GitHub Pages | The GitHub Blog
2009: [Wayback] CNAME support for GitHub Pages | The GitHub Blog
[Wayback] GitHub Pages Documentation – GitHub Docs
- [Wayback] Getting started with GitHub Pages – GitHub Docs
  - [Wayback] About GitHub Pages – GitHub Docs
  - [Wayback] Creating a GitHub Pages site – GitHub Docs
  - [Wayback] Adding a theme to your GitHub Pages site with the theme chooser – GitHub Docs
  - [Wayback] Configuring a publishing source for your GitHub Pages site – GitHub Docs
  - [Wayback] Changing the visibility of your GitHub Pages site – GitHub Docs (you need to have at least a GitHub Enterprise Cloud subscription for this).
  - [Wayback] Creating a custom 404 page for your GitHub Pages site – GitHub Docs
  - [Wayback] Securing your GitHub Pages site with HTTPS – GitHub Docs
  - [Wayback] Using submodules with GitHub Pages – GitHub Docs (I skipped this as the site will contain just one or a few pages)
  - [Wayback] Unpublishing a GitHub Pages site – GitHub Docs
- [Wayback] Configuring a custom domain for your GitHub Pages site – GitHub Docs
[Wayback] GitHub Pages | Websites for you and your projects, hosted directly from your GitHub repository. Just edit, push, and your changes are live.
- [Wayback] Setting up a GitHub Pages site with Jekyll – GitHub Docs (I skipped this for now given the simplicity of the pages to be published, but might later revisit in case I want to have a more complex pages site)
[Wayback] html – Can I create more than one repository for github pages? – Stack Overflow
[Wayback] domain – Publishing more than one site on GitHub Pages – Web Applications Stack Exchange
[Wayback] GitHub Pages is a CI/CD pipeline | Opensource.com
[Wayback] Tutorial: How to set up and automatically deploy your website to GitHub Pages – Roelof Jan Elsinga
[Wayback/Archive.is] Deploying documentation to GitHub Pages with CI | CircleCI

The goal is to have a githubstatus.wiert.me plain html (or maybe markdown) page that eventually will show some status information (kind of like githubstatus.com, but for different things).

Note that for free accounts, private repositories cannot publish pages: [Wayback] Troubleshooting custom domains and GitHub Pages – GitHub Docs:

GitHub Pages is available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see “GitHub’s products.”

[Wayback] GitHub’s products contradicts this by limiting GitHub Pages to only GitHub Pro and GitHub Team and higher levels.