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

Remove the Try it out section #30

Closed
TomasHubelbauer opened this issue Jul 6, 2018 · 1 comment
Closed

Remove the Try it out section #30

TomasHubelbauer opened this issue Jul 6, 2018 · 1 comment

Comments

@TomasHubelbauer
Copy link
Member

Should we? It won't work without CORS buster, at least with the placeeholder repo URL. Or we could replace that with one that will work in the browser.

@billiegoose
Copy link
Member

billiegoose commented Jul 6, 2018

Hold on. It'll be back soon. 😉

I need to wait 1 or 2 days to make sure I've stopped whichever server (I assume it is cors-buster, but it could also be webtorrentify-server or even signalhub) is hogging all the bandwidth. My billing cycle restarted yesterday, and today I was already at 8GB of bandwidth. I've gone through and deleted all the servers that I definitely don't need, and scaled the ones I suspect could be bandwidth heavy to 0 instances.

If tomorrow I'm still at 8GB (it hasn't gone up) then I will flip the switch on a new CORS proxy that is hardcoded to only work for AJAX requests from isomorphic-git.github.io. This means all the demos on the site will work again!

Then if that goes alright, I may try loosening the restriction further, to allow any domain as long as they are legit "git" requests. (I still find it hard to fathom 5 terabytes of cloning, so I suspect it was being used for "other" activity.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants