Closed kittsville closed 6 years ago
I personally use https://www.netlify.com/ to host mine. Works well too, and easier to set up than CloudFlare I found.
That does look pretty nifty. Might have to check it out for my own sites ๐ ๐ฏ
Does anyone know where the domain (http://queer-code.org/) is registered? I think most of the steps for adding HTTPS support (however we do it) are pretty straightforward(ish) but will require us to modify the nameservers...?
GitHub is (slowly) rolling out https on custom domains. They've not officially announced it yet, but many people are getting the option.
It was announced ๐ (via @lucymhdavies ) https://blog.github.com/2018-05-01-github-pages-custom-domains-https/
I do have access to the DNS entries. Let me know what to change, when you agreed on what to do.
Based on: https://blog.github.com/2018-05-01-github-pages-custom-domains-https/
If we're using CNAME
or ALIAS
we just need to change the settings to 'Enforce HTTPS' on GitHub.
If we're using A
records we need to update IP addresses too.
It's not very clear but I think the IP addresses are here: https://help.github.com/articles/setting-up-an-apex-domain/
You can't use CNAME
on apex domains (foo.com
/bar.foo.com
) so, unless our registrar supports the ANAME
/ALIAS
fakey records, it'll likely be A records.
The new IP addresses are:
185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153
Note:
first remove and then re-add your custom domain to the repository youโre using to publish your Pages site to trigger the process of enabling HTTPS
So someone needs to delete then re-add this file after the new A records have propagated (can take a few hours): https://github.com/QueerCodeOrg/queercodeberlin.github.io/blob/master/CNAME
I just updated the A records to the new ip adresses. CNAME
is only supported for subdomains. They have an option to use a custom nameserver. Interesting?
If you want me to do anything, don't hesitate to contact me directly via email. Github notifications aren't catching my attention these days.
No shit! It's secured!
You can serve QCL over HTTPS (for free) by putting CloudFlare in front of GitHub Pages like so.
It's what uve's NBit conference website used. I also use it on a few personal sites.