Skip to content
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

storybook.js.org #2304

Merged
merged 1 commit into from
Sep 5, 2018
Merged

storybook.js.org #2304

merged 1 commit into from
Sep 5, 2018

Conversation

shilman
Copy link
Contributor

@shilman shilman commented Sep 4, 2018

Move storybook to netlify to simplify our docs publishing flow

...as part of simplifying our docs publishing flow
@shilman shilman changed the title Move storybook to netlify storybook.js.org Sep 4, 2018
@indus indus added the question label Sep 4, 2018
@indus
Copy link
Member

indus commented Sep 4, 2018

This should be approved by @mnmtanish. He has requested the domain. Otherwise it is hard for me to know this is legit.
If he is no longer working for the project, another option would be to remove the CNAME in the repo. But that would make your site unreachable until I continue to process the request. I just want to amke sure nobody kidnaps the subdomain of someone else ;-)

@shilman
Copy link
Contributor Author

shilman commented Sep 4, 2018

@indus Awesome, thanks so much for your help. @mnmtanish is a friend and I've asked him to approve it via FB/slack/etc, so hopefully he'll comment here soon.

If not, we can do the CNAME option or take another approach to proving project ownership (e.g. I'm a github admin for the package, have published all the releases on NPM for the past year, etc. etc.).

@thani-sh
Copy link
Contributor

thani-sh commented Sep 5, 2018

Hi @indus, @shilman is maintaining this project now. Can you go ahead and make the change. Thanks.

@indus indus added organisation This PR/issue is regarding a target on a GitHub organisation change This PR/issue is regarding making a change to an existing subdomain external page This PR has a target of a site that isn't GitHub Pages and removed question labels Sep 5, 2018
@indus
Copy link
Member

indus commented Sep 5, 2018

I've made the changes and will take @shilman as authorized for further changes.
I now get a "not found" message. You propably have to configure netlify correct.

I'm not sure you have noticed, but there is a second subdomain "storybooks" that still directs to the Github-Page

@shilman
Copy link
Contributor Author

shilman commented Sep 5, 2018

Ugh, sorry about this. Working with Netlify to get this resolved on that side!

@indus
Copy link
Member

indus commented Sep 5, 2018

Looks good to me now. Welcome back https://storybook.js.org

@shilman
Copy link
Contributor Author

shilman commented Sep 18, 2018

Hi @indus! Thanks so much for your help and I have a small follow-up request here. Currently storybook.js.org is going through both the netlify CDN and also the cloudflare CDN. I'm told by Netlify that this can cause caching issues and other potential issues. Would it be possible to bypass Cloudflare for this domain? It's a single setting in Cloudflare:

cloudflare_dnsonly

It's possible that the site will be off SSL temporarily, but the team and I are OK with that. Documenting here storybookjs/storybook#4126 (comment).

Many thanks!

@shilman shilman deleted the patch-1 branch September 18, 2018 19:24
@indus
Copy link
Member

indus commented Sep 19, 2018

Just make a pull request andadd a comment //noCF in the end of your line. FYI: https://github.com/js-org/js.org/blob/master/cnames_active.js#L18-L23 (it says "make Cloudflare forward all requests directly to GitHub" but in your case it is of course netlify)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change This PR/issue is regarding making a change to an existing subdomain external page This PR has a target of a site that isn't GitHub Pages organisation This PR/issue is regarding a target on a GitHub organisation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants