Great. It took some effort to change my previous setup via cloudflare to just github.
If you host it on an apex domain, so no subdomain, you need to change the A record to point to github. When you have to wait for the records to be properly propagated to github. Assume it takes the full TTL for that. After change to have to remove the custom hostname, wait awhile until github reports the site is published to github.io. And then change the custom hostname again, and wait. After a while it should finally detect HTTPS possibilities and will generate a certificate for it.
For me to took about 2 hours to get this move working.
Brian Rinaldi is a Developer Experience Engineer at LaunchDarkly with over 20 years experience as a developer for the web. Brian is active in the community running CFE.dev and Orlando Devs.
Great. It took some effort to change my previous setup via cloudflare to just github.
If you host it on an apex domain, so no subdomain, you need to change the A record to point to github. When you have to wait for the records to be properly propagated to github. Assume it takes the full TTL for that. After change to have to remove the custom hostname, wait awhile until github reports the site is published to github.io. And then change the custom hostname again, and wait. After a while it should finally detect HTTPS possibilities and will generate a certificate for it.
For me to took about 2 hours to get this move working.
Thanks for sharing the details. Yeah. I didn't move mine yet as I suspected something like this.