Hi,
this is my first MM module and may others find it useful 
Download and infos: MMM-RepoStats
It’s about repository statistics for Docker, GitHub or GitLab repositories:
GitLab with private data (access token needed):
Let me know if something is missing or not solved in the right way, any feedback is appreciated.
Thanks,
Karsten.
@bugsounet said in Questions about update:
Its very poor to read this from a developer
is there a difference between running an old system and running a public forum without https?
my approach …
The following script must be executed in the magicmirror folder and creates another script restore.sh. This result script should be saved (on my server it is under git control) and can be executed (again in the magicmirror folder) to restore the old system (or bringing the old config to a new system).
#!/bin/sh
base="$(cd "$(dirname "$0")" && pwd)"
restore="$base/restore.sh"
config="${1:-config/config.js}"
css="css/custom.css"
modules="modules"
# Tests
[ -f "$base/$config" ] || (echo "config.js does not exists" && exit 1)
[ -f "$base/$css" ] || (echo "custom.css does not exists" && exit 1)
[ -d "$base/$modules" ] || (echo "modules directory does not exists" && exit 1)
echo "#!/bin/sh" > $restore
echo "" >> $restore
echo "base=\"\$(cd \"\$(dirname \"\$0\")\" && pwd)\"" >> $restore
echo "" >> $restore
echo "mkdir -p \$base/config" >> $restore
echo "mkdir -p \$base/css" >> $restore
echo "mkdir -p \$base/modules" >> $restore
echo "" >> $restore
echo "cat > \$base/$config <<\"EOF\"" >> $restore
cat <$base/$config >> $restore
echo "EOF" >> $restore
echo "" >> $restore
echo "cat > \$base/$css <<\"EOF\"" >> $restore
cat <$base/$css >> $restore
echo "EOF" >> $restore
echo "" >> $restore
for dir in $(find "$modules" -maxdepth 1 -mindepth 1 -type d)
do
[ -f "$dir/.git/config" ] && mods="$mods $(cat $dir/.git/config | grep 'url = ' | sed 's|.*url = ||g')"
done
for repo in $mods
do
echo "cd \$base/$modules && git clone $repo" >> $restore
done
echo "" >> $restore
for repo in $mods
do
moddir="$modules/$(echo $repo | sed -r 's|.*\/(.*)|\1|g;s|.git||g')"
[ -f "$base/$moddir/package.json" ] && echo "cd \$base/$moddir && npm install" >> $restore
done
echo "Created restore script $restore"
chmod +x $restore
I think we should open an issue in the github repo to discuss the moment stuff there, if it should be replaced and with what. Found this article.
In the current mm release 2.16.0 request is still a dev dependency but it is now totally removed on the develop branch (and so in the next release).
it’s not repo specific but attached to the user, see https://github.com/sdetweil
@ViDiBi said in MMM-RAIN-MAP:
lon: 11.91
I think you have a typo in your config, lon: 11.91 should be lng: 11.91
you can put this into css/custom.css file:
.newsfeed-desc {
display: none;
}
yes, and AFAIK you are using npm install --only=prod. This is may a thing to be mentioned in the docs because 99% of the users don’t need the dev dependencies …
thats amazon …
had a docker image containing Alexa Voice Service but because of more and more limitations I gave up a few months ago.
The sandbox error is mentioned in this github electron issue. It’s a chromium bug and everything should still work normally.
can you access the mirror with https://<ip-of-pi>:8080?
May you are using a client which is not in the ipWhitelist? You can test this with setting ipWhitelist: [], in your config.js.
the cors policies are more restricted with newer chromium releases and therefore in electron too.
There are already some issues here 1, 2 …
If HomeAssistent and mm are running on the same pi this may works when changing the host in the module config to localhost or 127.0.01.
In other cases it will be difficult to access the picture urls from inside the <module-name>.js file, accessing them from the node_helper.js should work. So one solution could be to fetch them with node_helper.js to a mm directory and use these urls in <module-name>.js.
Because I have no HomeAssistant I can not test this so this are only my thoughts so far …
yes, and AFAIK you are using npm install --only=prod. This is may a thing to be mentioned in the docs because 99% of the users don’t need the dev dependencies …
I used npm ci for a while. Because the package-lock.json format changed meanwhile I had problems with npm ci --no-optional with node 14, so I switched back to npm install.
But main point is you don’t get needed updates, e.g. we had in October an electron update because of invalid certs, in this case you had to use npm install.
As this is no direct part of the code we could update the documentation and explain both variants but I would prefer npm install as the default variant. Everyone who knows the difference can use what he wants.
you must access the site with https, e.g. https://192.168.0.143:8080/remote.html
didn’t know this but I’m not surprised …
When this limitation is live the modules must send the new header, we will see which of them are still maintained …
min. Version for node is v14, recommended v16. You have to update node.