RawGit is going away: redirect your content before October 2019 (it does disappear after that)
Posted by jpluimers on 2019/02/04
[WayBack] RawGit: RawGit served raw files directly from GitHub with proper Content-Type headers.
This means you have to redirect your existing RawGit links before October 2019, and you cannot add new links on RawGit.
You might want to try alternatives, for instance this one I mentioned in 2017: raw.githack.com – like rawgit.com but supports bitbucket as well and runs on plain nginx.
raw.githack.com serves raw files directly from GitHub, Bitbucket or GitLab with proper Content-Type headers.
There are some other options that RawGit itself mentions:
What you should use instead
The following free services offer fantastic alternatives to some or all of RawGit’s functionality. You may like them even more than RawGit.
RawGit source is still at [WayBack] GitHub – rgrove/rawgit: Served files from raw.githubusercontent.com, but with the correct content types., so if you want to host your own alternative you can.
It means I need to change these pages:
- Hosting an HTML gist containing JavaScript
- Decode URLs from The Great Suspender after a browser restart fails to reload them
- Work around G+ “403. That’s an error.” errors
–jeroen
The Wiert Corner - irregular stream of stuff 
Leave a comment