-
Notifications
You must be signed in to change notification settings - Fork 510
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
Redirect website to real root domain #146
Conversation
For "reasons", we don't actually have a CNAME set up in GitHub. The result is that GitHub doesn't know that pytorch.org/captum should actually redirect to captum.ai. This change puts a bit of JS on every page in prod that will do that redirect. We should fix it properly but at least we'll have something in place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
FYI: don't forget to rebuild & deploy the website to pick this up (generally should treat that gh-pages branch as a build artifact, I won't send any PRs against it) |
Looking to have automatic deploys to captum.ai from master, but running into some snags at https://circleci.com/gh/pytorch/captum/1867 cc'ed @jlin27 and @JoelMarcey on this, since I'm not sure what we need to setup in CircleCI to have |
I think we are on our way to solving this - might have been a misnamed env variable in the config. |
Summary: Same as pytorch/captum#146 Fixes #300 Pull Request resolved: #306 Reviewed By: Balandat Differential Revision: D18231026 Pulled By: Jakepodell fbshipit-source-id: d93a2e1f82c87b6b79fbfc17fe3fbc78c4229679
Redirect website to real root domain
For "reasons", we don't actually have a CNAME set up in GitHub. The
result is that GitHub doesn't know that pytorch.org/captum should
actually redirect to captum.ai. This change puts a bit of JS on every
page in prod that will do that redirect. We should fix it properly but
at least we'll have something in place.