Read the statement by Michael Teeuw here.
new script for mirror release upgrades
-
as we get more users, we see the same errors occurring after each quarterly upgrade…
i have started a script to do this for the users…
lets collaborate and get it working…
I’ll maintain a copy on my dropbox…
https://www.dropbox.com/s/71xtxr18si7cpnq/upgrade-script.sh?dl=0right now it doesn’t DO the npm installs… (flag for that)
we need to determine which files are important on the git pull ( i use fetch/diff to get the list of changed files)
and what to do about them… reset hard or stash /stash pop after…know that package.json, package-lock.json and custom.css are files of concern so far…
it find all modules which have a package.json, and goes into each and does npm install if the base npm install works…
we know that some modules are difficult , because their electron version must match the base…
how can we detect that and run electron-rebuild… -
Thanks for your hard work Sir 🤙🏾
-
@dazza120 my pleasure…
-
we know that each release WILL modify package.json (at least version number)
typically changes to package.json are because someone installed extra modules (npm install ??? will update the file)
-
and another question
I have 20 modules installed in the modules folder… but only 2 are active that have package.json files.
should we upgrade ALL of them? or only the active ones…(with disabled: false)
I suspect that most of the time, the list will be the same either way. mine is weird cause I help others with module problems by installing them myself (and don’t erase for a while)
one point to note here
to get JUST the enabled ones, we need to run a tiny javascript file, (so it will take two files)
otherwise we can do this all in bash -
see my post containing link to the new script
https://forum.magicmirror.builders/topic/10859/new-upgrade-script-ready-for-testing
