|
- What Are the Steps to Move Content from GitHub to JsDelivr?
From what I can tell, the steps to move content from GitHub to JsDelivr are the following: Fork from https
- How to choose a CDN to load JavaScript CSS libraries
via jsdelivr, with "latest patch version" feature compression: brotli size: 32 2 kB cache-control: public, max-age=604800, s-maxage=43200 The important difference here is the cache-control value, where the exact version gets a max-age of 1 year, while the other gets a max-age value of 7 days
- how to delete or update script on cdn. jsdelivr. com?
the thing i have done is change the code in github, but after i check in cdn jsdelivr com it is still the same and not changed Edit: jsdelivr com has update after 3 hours, after im edit on github com Github: code on github after change jsdelivr: code on jsdelivr com still not change
- jsdelivr doesnt update github commits - Stack Overflow
From jsDelivr's website regarding GitHub CDN We use a permanent S3 storage to ensure all files remain available even if GitHub goes down, or a repository or a release is deleted by its author Files are fetched directly from GitHub only the first time, or when S3 goes down
- Newest jsdelivr Questions - Stack Overflow
Ask questions, find answers and collaborate at work with Stack Overflow for Teams Try Teams for free Explore Teams
- git - Is it possible or no to use github private repository for web . . .
I used github-free account and already know how to access my web asset on github repo-public via jsdelivr, then i want make it private when i set the repo to private it not work, the assets cannot be accessed "failed to fetch" My idea is : Create private repo for web assets create branch that containing: branch css, branch js, branch webfonts
- Difference in JSDelivr URL with without latest
The caching time is the same in both cases - 12 hours at the CDN level and 7 days in the browser: cache-control: public, max-age=604800, s-maxage=43200
- tensorflow. js - How can I fix the DevTools failed to load SourceMap . . .
I had a similar problem when I was trying to work with coco-ssd I think this problem is caused by the version
|
|
|