Closed dschwoerer closed 3 years ago
The raysect.org domain redirects to github (where the docs are hosted) are handled by our domain provider. There is no option for https forwarding. I'm not going to pay and manage a host simply to redirect one domain to another domain.
As neither raysect nor cherab sites handle user secrets, there is no fundamental need to use https.
Turns out github now supports custom domains, I'll see about migrating the setup in the future.
I was just about to comment that you can just change to cname, and github will sort the certificate. I do agree, paying extra would probably not be worth it.
I've reconfigured github pages and the domain DNS. HTTPS should now be supported. The URL is now cleaner too as github redirects to raysect.org domain. Could you check it is working for you? If so, I'll close the issue.
Thanks, much nicer now :+1:
This breaks linking for external projects (like https://github.com/cherab/core/issues/314) but also from within github with extensions like https everywhere.
https://letsencrypt.org/ could be used to get certificates. Please let me know if there is something I can do to help.
PS: I would have reported this at https://github.com/raysect/documentation but the issue tracker there is disabled ...