Redirect to the docs site from https://pr.omethe.us/pyked

[bryanwweber]

https://stackoverflow.com/questions/9082499/custom-domain-for-github-project-pages/9123911#9123911

[bryanwweber]

Also https://help.github.com/articles/using-a-custom-domain-with-github-pages/

[bryanwweber]

Also, just noticed, Issue #100! Woo!

[bryanwweber]

Or maybe just add a link to the homepage?

[kyleniemeyer]

I could pretty easily redirect something like https://pyked.pr.ometheus.com, I think; the host allows me to create subdomains, and those are easy to redirect.

[kyleniemeyer]

Nvm, that was actually pretty easy... try https://pr.omethe.us/pyked now!

[kyleniemeyer]

I did this via a "meta refresh": <meta http-equiv="refresh" content="0; url=https://pr-omethe-us.github.io/PyKED/">

[bryanwweber]

Nice! Any idea whether the meta-refresh is preferred over setting the domain parameters? I barely understand any of this so I have no idea

[kyleniemeyer]

So, if you make the change at the domain level (i.e., with the website host), I think a redirect would happen before the browser even sees the HTML of the page (which is where the meta-refresh happens).

But I think I can only do a domain-level redirect for a subdomain.

[bryanwweber]

Ah, now I remember what I was thinking here. In this answer: https://stackoverflow.com/a/22374542/2449192 it is possible to redirect and respect the paths, so https://pr.omethe.us/ would redirect to https://pr-oemethe-us.github.io and https://pr.omethe.us/PyKED would redirect to https://pr-oemethe-us.github.io/PyKED and so forth. But obviously, that's not necessary and this solution seems perfect! Now we just need some content for the homepage 😄