• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
MagicMirror Forum
  • Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.

Backing up via GitHub repo

Scheduled Pinned Locked Moved Troubleshooting
19 Posts 6 Posters 3.9k Views 6 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Away
    sdetweil @arnedebeer
    last edited by sdetweil May 21, 2020, 1:05 PM May 21, 2020, 1:04 PM

    @arnedebeer you can, but private repo is not free

    i backup the MM folder to my PC, then delete the node_modules folders where I find them
    and then zip the thing onto an external drive, that is backed up to the cloud.

    so I have 3 layers of backup, pc, external disk and cloud

    i have 2 external drives, 5 and 8 terabytes. and sometime copy from one to another for another layer.

    on my pc, I run two 4tb drives in raid 0, so if one dies, I can get the data back
    I do my cloud back ups with backblaze, as it does continuous incremental backups…

    on my critical mirror devices, I have gone to booting the sd card, but running from SSD disk.
    so the sd card usage is minimal.

    Sam

    How to add modules

    learning how to use browser developers window for css changes

    A 1 Reply Last reply May 21, 2020, 2:43 PM Reply Quote 1
    • A Offline
      arnedebeer @sdetweil
      last edited by May 21, 2020, 2:43 PM

      @sdetweil a private repo on GitHub is free though!

      S 1 Reply Last reply May 21, 2020, 2:48 PM Reply Quote 0
      • S Away
        sdetweil @arnedebeer
        last edited by May 21, 2020, 2:48 PM

        @arnedebeer well, then, didn’t used to be… I see its changed… thanks…

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        A 1 Reply Last reply May 21, 2020, 8:28 PM Reply Quote 0
        • A Offline
          arnedebeer @sdetweil
          last edited by May 21, 2020, 8:28 PM

          @sdetweil perhaps your four layer backup routine isn’t needed after all!:winking_face:

          S 1 Reply Last reply May 21, 2020, 8:46 PM Reply Quote 0
          • B Offline
            bhepler Module Developer
            last edited by May 21, 2020, 8:41 PM

            In all honesty I don’t think it’s necessary to back up your entire Magic Mirror. If you back up the config.js file, you can rebuild your mirror pretty quickly. It will contain all of your API keys and a list of the modules you have installed. The hard part will be locating the Github repos to clone the repositories.

            And you did star all of the module repositories you need, right? That would put them all on a very convenient web page.

            A 1 Reply Last reply May 22, 2020, 12:31 PM Reply Quote 0
            • S Away
              sdetweil @arnedebeer
              last edited by May 21, 2020, 8:46 PM

              @arnedebeer well, there is a LOT of stuff on this machine… lots more than MM…

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              1 Reply Last reply Reply Quote 0
              • A Offline
                arnedebeer @bhepler
                last edited by arnedebeer May 22, 2020, 12:32 PM May 22, 2020, 12:31 PM

                @bhepler I think you’re quite right to be honest. But by forking the entire project this won’t be possible, that’s why I was hoping it was possible to create a repo for it to automate the backup.

                Perhaps a better way to back my config up is to create a script that mails the config every x amount of time to myself :thinking_face: :thinking_face:

                B 1 Reply Last reply May 22, 2020, 4:24 PM Reply Quote 0
                • B Offline
                  bhepler Module Developer @arnedebeer
                  last edited by May 22, 2020, 4:24 PM

                  @arnedebeer - If you must. I make it a practice that I back up the config.js just before I modify it. That way I don’t have a dozen identical copies of the file sitting around. It also lets me easily see when was the last time I changed the mirror.

                  BitVise is good for this, as it will open a terminal window and an SCP window, which serves as a good reminder to copy the config file down before I do anything.

                  1 Reply Last reply Reply Quote 0
                  • K Offline
                    karsten13
                    last edited by May 22, 2020, 8:11 PM

                    you can do that with a git repo which is located above your MagicMirror git repo.

                    If you have a path structure e.g. ~/mm/MagicMirror where MagicMirror contains the MagicMirror-git-repo goto ~/mm and create a new git repo there with git init. Create a .gitignore file in ~/mm and put the line MagicMirror in it so this subdir is ignored.

                    Now you can add files or directories with

                    git add -f MagicMirror/config/config.js
                    git add -f MagicMirror/modules/*
                    

                    Then commit.

                    S 1 Reply Last reply May 24, 2020, 3:55 PM Reply Quote 0
                    • S Offline
                      sojourner
                      last edited by May 24, 2020, 3:49 PM

                      The MM repo has a git configuration to only track the “default” folder in the MM/modules folder. This is cool because you can have a separate git repository inside another! When you like a module someone (even yourself) created on github, you need to install it in the MM/modules folder. For example, from the MagicMirror/modules directory, I’m cloning a repo:

                      [MagicMirror/modules]> git clone https://github.com/sdetweil/MyCovid19.git
                      

                      You’ll see that a new directory is created under the “modules” directory – and it’s the same name as the git repository. Important to this discussion; the MagicMirror repo doesn’t care about this new directory! You follow the usual steps to update MM with no git side-effects … and … you can update the new module directory that you cloned using the same “git pull” process!

                      Side note: there are often a few more steps needed to install a module. In this example, @sdetweil follows best practice to include installation instructions in the module README.

                      So, in a general case, you can create a repo, for example, “MyStuff” in the MM/modules folder. It can contain anything and you can manage it (edit files/push/pull/branch/etc.) all within the “MM/modules/MyStuff” directory.

                      Just don’t call your repository “default”! :-b

                      fyi - Git keeps track of files/directories to ignore within a repository by using a .gitignore file located in the repo’s root folder. Check out all the files the MagicMirror ignores!

                      1 Reply Last reply Reply Quote 1
                      • 1
                      • 2
                      • 1 / 2
                      1 / 2
                      • First post
                        8/19
                        Last post
                      Enjoying MagicMirror? Please consider a donation!
                      MagicMirror created by Michael Teeuw.
                      Forum managed by Sam, technical setup by Karsten.
                      This forum is using NodeBB as its core | Contributors
                      Contact | Privacy Policy