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.

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

@bhepler

or

@retroflex thank you, your’re right.

Checked this again with this unmerged pr. With this pr, the config.js is no longer reachable per browser, so we have to wait for the next release where this is hopefully merged.

@Jessendelft other possibilities:

• you can whitelist the ip adresses which are allowed to access the mirror
• you run 2 instances of the mirror, one private restricted to localhost access and one public with content everyone is allowed to see

2 more things:

• the new branch you are using should start on the mm-branch develop (not master)
• when creating the PR on github you have to manually change the base branch from master to develop

These rules are specific to the mm-repo. Because of quarterly releases the master branch only changes 4 times in a year. The development between the releases is done on develop.

@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

it’s not repo specific but attached to the user, see https://github.com/sdetweil

you could use a proxy https://cors-anywhere.herokuapp.com/https://dd.weather.gc.ca/citypage_weather/xml/ON/s0000326_e.xmll, there is already such a line in the PullRequest merged today.

should be 23 (not 16)

you can do it with or without docker, thats your choice.

With docker you have to use different config.js files, they can be placed in the same folder and must be mapped into the right container.

You could use only one modules folder for all instances by installing all modules there.

Updating the core is done by using a new docker image (same for all instances).

The one-modules-folder may also could be established with the classic setup, you could use symlinks from a central place into the modules folder of the several instances (never tested this!).

2 more things:

• the new branch you are using should start on the mm-branch develop (not master)
• when creating the PR on github you have to manually change the base branch from master to develop

These rules are specific to the mm-repo. Because of quarterly releases the master branch only changes 4 times in a year. The development between the releases is done on develop.

@sdetweil no

may using esm library is one approach as described e.g. here https://blog.logrocket.com/how-to-use-ecmascript-modules-with-node-js/

@lavolp3

• rename node_helper.js to node_helper.mjs

worked in my test (did not do anything with the imported axios, but mm starts).

Link should work now, forgot to make it public

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.

@florianrd The komoot api is not public so I asked them to get a key. They answered that the api is only available for partners and provided a website for becoming a partner.

So I sent another mail to the partner mail adress (2 weeks ago) and never got an answer …

@sdetweil I think he deleted here as much as possible intentionally. He left in anger and is starting a new one man show here

everything o.k., the : was a typo here …