note the missing g
libconf-2-4
should be
libgconf-2-4
note the missing g
libconf-2-4
should be
libgconf-2-4
the new installer referenced here is now part of the base at 2.8.0, released July 1, 2019
Maybe it could live on another branch so users could type git checkout experimental to opt into the new features.
certainly this would be a good approach
@egnos comma is continuation… its ok to have an EXTRA , after the play group,… it is NOT ok to have a missing , between things
@bhepler we should start a new script for upgrades
installers/upgrade
#!/bin/bash
# change to MagicMirror folder
cd ~/MagicMirror
# get the latest upgrade
if git pull; then
# update any dependencies for base
if npm install;
# process updates for modules after base chnaged
cd modules
# get the list of modules with package.json files
find -maxdepth 2 -name 'package.json' | while IFS= read -r FILE; do
echo "processing for module " $(dirname $FILE)
# change to that directory
cd $(dirname $FILE)
# process its dependencies
npm install
# return to modules folder
cd - >/dev/null
done
return to Magic Mirror folder
cd - >/dev/null
fi
else
echo git pull failed
# return to original folder
cd - >/dev/null
fi
I have reported this, hopefully someone from the website team will look into this
and for the future, if u have problems with config.js syntax errors, in the MagicMirror folder run
node tests/configs/check_config.js
it will report the problems. start & fix from the top
edit: wrong name for the checker… (removed extra s on the end)
@mrshu i just need some more testers… the screen saver and pm2 changes are newer…
I want this to BE the installer script…
and my updater too
and maybe the pm2 standalone script
yes, logging will help everyone.
@peterbarlow2000 the node_helper file gets executed on the server, (one instance for all clients)
and the file in the module folder that matches the module name (modulename.js we call it)
runs on the client (one instance for each client)
I would change this
code needs to be executed on the client (by electron?).
to
code needs to be executed on the client (in the browser?).
yes, some of the platforms (Pi Stretch for example) are not installing npm and/or node as part of their initial installs…
see here https://www.battlehillmedia.com/installing-node-js-and-npm-on-raspberry-pi-3/