You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want to host these on your local network, you probably would need to rewrite the DNS response for mrchromebox.tech to use the scripts "as is" because they "self update" when run, but that still won't help with the binary files.
Another plan is to fork this repository, change or comment out the lines where the scripts set the base URL to mrchromebox.tech and run your webserver against your local clone of your forked project.
The problem is these scripts are referencing LOTS of files also hosted by MrChromebox, the lines below are used by a majority of the functions to find the right files (out of hundreds available).
So unless you want to only support one or two models of Chromebook/Chromebox and hardcode those into your fork of the scripts, you will need to have a fair bit of storage for the binary files.
It seems easy, that if this line was changed to script_url="${script_url:-'https://raw.githubusercontent.com/MrChromebox/scripts/master/'}" then you could do the following, but you won't have the rw_legacy/firmware binaries/etc unless you mirror the rest of the files as well.
Activity
dragon788 commentedon Oct 25, 2021
If you want to host these on your local network, you probably would need to rewrite the DNS response for mrchromebox.tech to use the scripts "as is" because they "self update" when run, but that still won't help with the binary files.
Another plan is to fork this repository, change or comment out the lines where the scripts set the base URL to mrchromebox.tech and run your webserver against your local clone of your forked project.
scripts/firmware-util.sh
Line 15 in c0c33ba
The problem is these scripts are referencing LOTS of files also hosted by MrChromebox, the lines below are used by a majority of the functions to find the right files (out of hundreds available).
scripts/sources.sh
Lines 9 to 15 in c0c33ba
So unless you want to only support one or two models of Chromebook/Chromebox and hardcode those into your fork of the scripts, you will need to have a fair bit of storage for the binary files.
It seems easy, that if this line was changed to
script_url="${script_url:-'https://raw.githubusercontent.com/MrChromebox/scripts/master/'}"then you could do the following, but you won't have the rw_legacy/firmware binaries/etc unless you mirror the rest of the files as well.