Read the statement by Michael Teeuw here.
automatic update module by notification
-
@bdream if the module update adds a feature,
you don’t care, as u are not using it now
if the module update fixes a bug
you don’t care as u probably haven’t seen it
(else u wouldn’t have deployed the module in such a sensitive environment…)
I STRONGLY recommend,
If it’s working, don’t touch it.
-
@bdream said in automatic update module by notification:
I would prefer having an automatic to update in case it’s notified.
option1: Adding a new paramter “forceUpdate” to the notification module so that it does the update instead of the notification (someone has to code this)
option2: Write a bash script which iterates over the module folders doing something like this (in every module folder)
git reset --hard git pull [ -f "package.json" ] && npm install
This script should be executed e.g. daily by e.g. a cronjob.
As Sam already mentioned this would be the hard way, may its better not to change a running system and ignore the notification, your decision.
-
I recommend not updating MM or modules unless they work. Just leave them. Update them only when you find some issue or need a new feature.
-
@MMRIZE @sdetweil @bhepler @karsten13
many thanks for your comments, I really appreciate it!At first I will disable notification at my mothers MM. Hope there will not be a secure issue I oversee than. But it will anyway be an small one in my mothers environment.
For me I will play with “play” with the other options you mentioned and will see if this works for a longer time in a good way ;)
-
-
@bdream , Hi it’s already coded since some year but not published in this forum :beaming_face_with_smiling_eyes:
-
@bugsounet sounds good!
What is the midules name please?