Read the statement by Michael Teeuw here.
The correct way to update a module
-
I’ve had the notification on the top bar saying there’s an update to my MMM-calendarExt3 module, that the current installation is 2 commits behind the main branch.
What is the correct way of dealing with this?
It may seem a daft question however…
The last time I had an update the issues off the back of it - when the update ran into issues and failed part way - and the entire MM stopped working and some kind people on here rescued me from the point of binning the whole setup.
Cheers.sdetweil edit: change topic name
-
@JMac in this case, if you’re that close, it’s a simple
git pull
in your module directory, then restart.as a force of habit, I run
git pull
thennpm install
on every update, just to make sure everything loads, then restart.Likely, the reason it didn’t work before was a slight change to the code introduced in 1.2.0 - MMRize took duplicate code out of all his CX3 modules, and made a single file for them all - you had to install that code via the documentation here: https://github.com/MMRIZE/MMM-CalendarExt3Agenda#update-to-120
I missed it too…
-
cd <YOUR_MM_DIRECTORY>/modules/MMM-CalendarExt3 git pull npm install
When you meet some error message about
CX3_Shared
, try this also there.git submodule update --init --recursive
-
@MMRIZE you should add a postinstall npm task and check that and do the git commands
-
@sdetweil
I did already, so most cases it will work unless missing ‘npm install’ -
@MMRIZE ah…
-
@MMRIZE When I cd MagicMirror I get into that directory
but the /modules/MMM-CalendarExt3 says it isn’t recognised. -
@JMac not /modules
/ at the front means root
you want ~/MagicMirror/modules/MMM-CalendarExt3
~ at the front means current users home folder
if you are in the MagicMirror folder, then
cd modules
will move the current folder the the ~/MagicMirror/modules folder