-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Site redirect #2
Comments
Thanks for doing that @karbassi! I made the changes to the domain configuration today, but the DNS needs some time to propagate. I'll check back in tomorrow and close this issue once I've confirmed it's working. |
Forgot to mention: I own todotxt.org as well as todotxt.com. I'd forgotten about this! So for now I just forwarded the .org to .com, but putting out there that it's available to us if we want to use it differently at any point in the future. |
@ginatrapani Idea, how about doing the reverse since the project has moved to an org. Having todotxt.com redirect to todotxt.org (which points to this repo) |
Yep, I think that's a good idea. I'll PR the CNAME update, and when that's merged I'll update the DNS config. |
Also there's the Tumblr blog located at http://blog.todotxt.com/ I can make this blog.todotxt.org when we make this switch. |
@ginatrapani all sounds good. The CNAME is merged and we wait for DNS to propagate. Close this issue when https://dnschecker.org/#A/todotxt.com and https://dnschecker.org/#A/todotxt.org are working. |
Okay, I've updated the DNS config. todotxt.org is resolving but the forward from todotxt.com -> todotxt.org is taking longer. I'll keep an eye on it, and leave this open until I've confirmed it's working. |
I just checked the DNS propagation and it's propagated across the world. Closing. |
@ginatrapani I've moved over the
gh-pages
from thetodotxt-cli
project into this repo. The CNAME points totodotxt.com
.Next step is to have the domain to point to GitHub servers.
https://help.github.com/articles/setting-up-an-apex-domain/#configuring-an-alias-or-aname-record-with-your-dns-provider
The text was updated successfully, but these errors were encountered: