Github Pages with custom domainsUp to now, the procedure to serve these sites via Github with a custom domain was the following:
- create an A-record in the domain providers' DNS (that's independent of Github) containing Github's IP addresses (they provided two different for availability / scalability reasons)
- create a CNAME file in the Github repo containing the domain name in uppercase (oftentimes that was created automatically by the appropriate Github repository settings dialogue.
- commit, push and done.
How to Migrate to httpsTo migrate this to the new https system, follow these steps:
- change the DNS A-record(s) at your domain provider to the new Github https address (now they provide four different IP's instead of the previous two) - e.g. 220.127.116.11, 18.104.22.168 etc.
- Remove the old CNAME file from your repository, commit and push this deletion to Github.
- Open the Github repository settings page and manually enter the domain name.
- Wait a few minutes until your certificate is generated - invisible for you.
- If you're using Jekyll to generate your site, it's a good idea to change your
_config.ymlconfiguration from "http://yourdomain" to "https://yourdomain". That's not absolutely required, but will ensure that Jekyll will use the more secure https protocol for all cross-references on your site.
- Now you can check the "enforce https" checkbox - which was disabled until this very last step