Add proxying to github for non-existing local assets #58
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the existing implementation, you need to cache all the possible assets locally, or you won't be able to use them. This PR adds a way for end-users to use locally cached assets and, at the same time, enjoy an occasional non-cached asset.
I'm unsure if including this change in the main docker image is worth it: adding a new docker tag for non-security cautious people/environments where this will be enabled might be a better idea. Or maybe setting up an nginx server on a different port just for that. Please advise how you would like to proceed here.
I'm using netboot.xyz in a tiny just-for-fun homelab environment, and I very much enjoy having a few most-used assets in the local cache and still being able to boot any other available thing :)