So I have a question about backup

[Ray]

@sdetweil that’s fantastic. I appreciate the quick response. I put a lot of effort and time in this mirror
so is good to hear. I can back it up safely

[Ray]

@sdetweil forgot to ask
so the git remote -v
we’ll get all its information from my original config.js
is that correct

[sdetweil]

@ray you do that in each module folder
the info from config.js is settings and API keys for each/all the modules

my grandson just went home from.sleepover. I can write a quick script to backup and restore

[karsten13]

see also https://forum.magicmirror.builders/topic/14255/what-is-your-backup-and-restore-method

[sdetweil]

@ray i created two scripts mm_backup and mm_restore
you can get them here

they write/read from a folder (defaults to ~/MM_backup )

using ~/MagicMirror as the source (default)

(but take parms to change the names) see mm_backup.sh -h

this creates a git repository of the 2 files and creates a tag (label) for the instance of the backup.

you should create a (free) private repo (to keep any config settings private) on github and push the local repo there to have an offline backup
then u can clone it anytime and restore from the appropriate tag (date/time)

[mumblebaj]

@sdetweil
Hi Sam. Here? I checked your Github and nothing there either. Or maybe I am missed it?

[sdetweil]

@mumblebaj doah!!.. forgot the link

https://github.com/sdetweil/MagicMirror-backup-restore

[mumblebaj]

@sdetweil Awesome. Thanks Sam. Always nice work from you.

[mumblebaj]

@sdetweil When I ran the mm_backup.sh I saw this error but it created the output in the MM_backup folder as expected.

usage: git init [-q | --quiet] [--bare] [--template=<template-directory>] [--shared[=<permissions>]] [<directory>]

    --template <template-directory>
                          directory from which templates will be used
    --bare                create a bare repository
    --shared[=<permissions>]
                          specify that the git repository is to be shared amongst several users
    -q, --quiet           be quiet
    --separate-git-dir <gitdir>
                          separate git dir from working tree

Is this because of some options that I did not specify? After the output was created I just manually pushed to a private directory on git.

[sdetweil]

@mumblebaj probably git version before 2.28

the primary branch name option didn’t come in til 2.28. 0

i have

git --version
git version 2.34.1

I will add a check…

to upgrade git (don’t do it for these scripts… I have fixed the script to not need this capability, just documenting how)

sudo add-apt-repository -y ppa:git-core/ppa
sudo apt update
sudo apt install git -y