Re^3: Using a git filter to Cache HTML Resources Locally

Replies are listed 'Best First'.
Re^4: Using a git filter to Cache HTML Resources Locally by haukex (Archbishop) on Oct 12, 2018 at 08:54 UTC
local caching without rewriting urls, ex `<script src="//cdn..../../../"` Maybe I'm missing something obvious here, but how would you do this for URLs like the ones I showed, e.g. `https://cdnjs.cloudflare.com/ajax/libs/normalize/8.0.0/normalize.min.css`? Remember I said these files are for public distribution, and I can't rely on people having a local server - it's even possible to open the HTML files from the local disk (`file://`). Using the public CDN URLs is easy, and doesn't require me to distribute a bunch of extra files along with my own. something like url_for('resource.js') in javascript or perl, to load resources based on configuration/environment Sure, that's a possibility - but then that code gets run for everybody. This tool is really only meant to be a development aid, it applies only to the local git working copy, and only when it's configured by the user. The files in the repository are those for distribution, and thanks to the filter they always keep their public CDN URLs. The only downside of the git filter approach that I can see so far is the small performance penalty on some git operations. So I'm not yet convinced that there is something wrong with this approach.	[reply] [d/l] [select]
Re^5: Using a git filter to Cache HTML Resources Locally by Anonymous Monk on Oct 14, 2018 at 07:21 UTC
Maybe I'm missing something obvious here, but how would you do this for URLs like the ones I showed, e.g. https://cdnjs.cloudflare.com/ajax/libs/normalize/8.0.0/normalize.min.css? Remember I said these files are for public distribution, and I can't rely on people having a local server - it's even possible to open the HTML files from the local disk (file://). Using the public CDN URLs is easy, and doesn't require me to distribute a bunch of extra files along with my own. Huh? The html files merely detect if a local cache exists, otherwise they load from internet So a wannabe developer, or clever end user, merely runs `cacheresources.pl` and they're set	[reply] [d/l]
Re^6: Using a git filter to Cache HTML Resources Locally by haukex (Archbishop) on Oct 14, 2018 at 07:30 UTC
Sorry, I don't understand what point you're making, and I've already replied on the topic of JS vs. a git filter (twice). Protocol-relative URLs appear to be widely discouraged now, and as I already said, don't seem to help in this case anyway. Could you maybe show some example code of what you mean?	[reply]
Re^7: Using a git filter to Cache HTML Resources Locally by hippo (Archbishop) on Oct 14, 2018 at 12:26 UTC
Re^8: Using a git filter to Cache HTML Resources Locally by haukex (Archbishop) on Oct 14, 2018 at 13:25 UTC
Some notes below your chosen depth have not been shown here
Re^7: Using a git filter to Cache HTML Resources Locally by Anonymous Monk on Oct 15, 2018 at 02:01 UTC
Re^4: Using a git filter to Cache HTML Resources Locally by Corion (Patriarch) on Oct 12, 2018 at 08:07 UTC
The interesting part is not the URL rewriting but the automatic download of the remote URL to a local file. It wouldn't be hard to try to load both URLs from Javascript, or whatever, but why add additional complexity when you can just rewrite the file?	[reply]
Re^5: Using a git filter to Cache HTML Resources Locally by soonix (Chancellor) on Oct 12, 2018 at 08:53 UTC
This remarks reminds me of a caching proxy I had in use when internet connection time was metered in seconds. It might be possible to configure it to the same effect. For shielding your "work in progress" from local resources (CSS/JS/...) that are WIP themselves, however, the git filter can do what the proxy definitely can't.	[reply]
Re^5: Using a git filter to Cache HTML Resources Locally by Anonymous Monk on Oct 14, 2018 at 07:03 UTC
The interesting part is not the URL rewriting but the automatic download of the remote URL to a local file. Heh Downloading/mirroring is the boring part :)(lwp-rget/wget/curl/httrack...) The URL rewriting is the eyebrow raising part (sourcefilter) It wouldn't be hard to try to load both URLs from Javascript, or whatever, but why add additional complexity when you can just rewrite the file? Um, ... Why is one additional complexity but not the other?	[reply]
Re^6: Using a git filter to Cache HTML Resources Locally by haukex (Archbishop) on Oct 14, 2018 at 07:22 UTC
Why is one additional complexity but not the other? Rewriting the HTML is optional and local, while using JavaScript is global.	[reply]