new update/upgrade script, ready for testing

gonzonia

pi@MagicMirror2:~ $ ls /etc/apt/sources.list.d
nodesource.list  raspi.list
pi@MagicMirror2:~ $ sudo cat /etc/apt/sources.list.d/nodesource.list
deb [arch=arm64 Pin-Priority=600 signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x nodistro main
pi@MagicMirror2:~ $ sudo cat /etc/apt/sources.list.d/raspi.list
deb http://archive.raspberrypi.org/debian/ bullseye main
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://archive.raspberrypi.org/debian/ bullseye main

sdetweil

@gonzonia thanks… same as I see…

gonzonia

@sdetweil

I’m just going to rebuild. I’ll let you know if I hit any snags. Thanks again.

Socrates

Sorry to revive this old thread, but I used this script to update all my modules at once, and they worked perfectly after upgrading Node.js and npm.
bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)”

I have a question: Will this script automatically check for and apply module upgrades periodically? Or is it better to add it to a nightly crontab?

sdetweil

@Socrates no… this script is only for the base.

sdetweil

@Socrates note that without adding a parameter
The script does nothing. It only tests the ability to update the base MagicMirror

Update is two pass process

Test. Make no changes
Do. Apply the changes (with the parameter apply)

Many users have modified MagicMirror base code not knowing about the config and css file design. These changes block the ability to update normally

Over time they forget that they changed the files and what they actually changed. The force way to install is to wipe all changes, but now the result doesn’t work like it used to. Adding a lot of frustration.