-
Notifications
You must be signed in to change notification settings - Fork 309
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
Discuss Serving Static Content From Another Server #345
Comments
This is still blocked with #343 with needs testing and now here. There's nothing to be sorry about. Don't work on this until fully documented with any presented 503s _(the toobusy-js package 503 main page does not apply here nor do times around scheduled redeployment)_ ... you need to do the same by posting maffs somewhere... screenshots won't be accepted...This will take some time to document as you've given it a whole half of a day to propagate caching to clients and no recent applicable proof. |
Starting this off.... jQuery. There are a few available CDNs that can handle this that are official.
EDIT: Discussing out loud with a sample source tree:
and so on and so forth.
Some rules:
|
The somewhere for maffs is now on our wiki in the maff subfolder. If you are unfamiliar with maffs please visit https://addons.mozilla.org/firefox/addon/mozilla-archive-format/ and please ensure that it is a single compressed zip with the .maff extension. It doesn't take a rocket scientist to save a page with this add-on. If you are using a different browser then you need to find one for that browser if available... if not then you have to do it in Moz... if no maffs are present then this issue could be closed with invalid... e.g. participation is optional but if you observe one save the page and save http://status.nodejitsu.com and post those in. This will track everything and don't worry about overwriting things there in that folder because the git visualization will handle that. As you can see @Zren I'm way ahead of you and I've given this quite a bit of thought. :) |
Maybe jsDelivr could help? |
What does that limit us to? CDNs that only serve their content on a subdomain? |
This part was difficult to word which is why it got appended to multiple times. Disable JavaScript and load the target url into the address bar in a new tab... if the resource doesn't show up properly (MIME type and all) due to a requirement of JavaScript being enabled then it's a no go.
Will check it out. I'm definitely interested in proper load balancing when an outage occurs. Thanks. |
Heads up... no one has posted any maffs or any other message regarding this issue. Possibly later today or tomorrow it will be closed. |
* Use proper usage of `maxLag` for process bump. * Add in simple referer check mentioned in OpenUserJS#343 to prevent SEO/abuse. * Remove separator from `./routesStatic.js` and let `join` do it's op. Closes OpenUserJS#345 **NOTE**: Server cloud services may already handle load balancing but keeping this in for the time being... if it crops up again, bump to a maximum of 175ms. toobusy-js does use timers that are never stopped even at the equivalient of `document-idle` event state. If this package proves long term to be an issue remove it completely... however during testing period it **PASSED**.
* Reinstate *toobusy-js*... at least one of their timers has been fixed on shutdown. See OpenUserJS#354, OpenUserJS#353, OpenUserJS#352 and base issue of OpenUserJS#345 ... loosely related to OpenUserJS#249 and attempt to address OpenUserJS#944 with a work-around... VPS should be faster than our old one so perhaps the timers don't make as much of a difference. Start with our old default lag value... this may introduce too many 503's again but hopefully not * Retested delete op * Bug fixes, tests, and docs updates... please read their CHANGELOGS * Shutdown the server on SIGINT * Modify db closure to not have dependents
503s are prominent enough that you'll get 2-4 every page load.
One 503 will break the entire page.
That cache is completely ignored if you get a 503.
Either have a seperate Apache server under a subdomain (eg: static.openuserjs.org) or use a public CDN.
Sorry Martii. Having the site be useful outweighs any security concerns of not hosting our own javascript.
We can host Ace locally (as it appears to not work on a CDN) but it's not on every page anyways.
The text was updated successfully, but these errors were encountered: