SOLVED Questions about update
Is it possible to know when the next update (from develop branch) will be merged on the master branch ?
When I use the git status command, here’s the result
pi@MagicMirror:~/MagicMirror $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Fichiers non suivis: (utilisez "git add <fichier>..." pour inclure dans ce qui sera validé) css/custom.css_backup modules/default/compliments/compliments.js_backup modules/default/compliments/compliments.json modules/default/compliments/compliments.json_backup aucune modification ajoutée à la validation mais des fichiers non suivis sont présents (utilisez "git add" pour les suivre)
Of course, I want to keep my backup files. Does I need to use git add to preserve my file ?
@selyjohns a new mm release is done every calendar quarter ( every 3 months).(Jan, Apr, July, Oct)
the next is Jan 1
no you do not need to use git to save your files. just copy them someplace outside the mm folder as a backup
the ones list are in the untracted section, meaning git sees them but is not managing them
for update, you can use my update script
I have a couple of tricks I use to preserve my modifications, even across a total system rebuild.
- config.js & custom.css is symlinked to my backup directory.
- my config.js is commented on where I can get my modules, and any forum posts which apply to help get them running (like how to add back required node.js modules that aren’t in MagicMirror core anymore)
- any and all non-core modules that have changes that would be overwritten by an update by the author are forked to my own github. if I update a core module, I would symlink the modified file to my backup directory.
- I left myself instructions in the backup directory on how to reset things I can’t/shouldn’t backup as of present (crontab, samba, config.txt, how to set up fresh SD card, hostname, etc) (config.txt you’ll see in the backup, but you shouldn’t just copy that back as new installs may be different in that file, use it to compare and add your changes)
- My backup directory is thrown to github in a private repository nightly using this (censored) script.
#!/bin/bash d=$(date +%Y-%m-%d) cd ~/<directory> cp /boot/config.txt config.txt.backup cp /etc/samba/smb.conf smb.conf.backup rm core git add * git commit -m "Nightly Backup"+$d --all git push https://BKeyport:<token>@github.com/BKeyport/<directory>.git
0 0 * * * /home/pi/<directory>/backup.sh 30 * * * * pm2 restart omx
(Run the backup script at midnight, and restart my camera cutout at 30 minutes past the hour respectively - OMX is a bit of a pain, working on better)
I would love to see user modules be in their own directory so I could just wholesale symlink that directory to my backup system, but, eh…
github (cheat sheet: https://education.github.com/git-cheat-sheet-education.pdf)
What a lot of effort… Do you do the same with your personal computer?
@bugsounet No effort at all, once it’s set up.
Takes the typical reload time of 5 hours down to an hour, including burning a new SD. About 10 minutes of setup to restart a messed up mirror.
MM update every 6 month… System update every month or less… Npm package update every month… Modules every month… Or not maintened… Yeah really I am
So I think you use very old system… And you are a module developer!
Its very poor to read this from a developer
Sorry., it’s not like this that you will learn beginer
Sample with your Old save… Just try to laun an update… It will take a lot of time! (apt-get update & & apt-get upgrade)
You will says… Yes but it’s not necessary… So don’t do any update on your computer too!
@bugsounet SD Card failed every month for a while. Got tired of having to rebuild from scratch and taking time to have to find how to do half the crap I do, because my memory is swiss cheese when it comes to CSS in particular.
Admittedly, my mirror is on a pi that does more than just the mirror, one of my files updates every couple of days. I do this to make it so I don’t have to think when I make major changes.
It’s a suggestion. Leave it at that, eh?
karsten13 last edited by
@karsten13 Make all things like me after you can talk
Yes, it’s a good solution that works great once installed.
To build my MM, I have made some modifications on everywhere to obtain the result I want, and if i had to rebuild all it will take a lot of time because it’s impossible to remember everything (like modifications on boot.txt)
And I agree about SD Card. It’s a really difficult to preserve it. So the solution is to externalize backups.
I’ve a NAS server with NFS possibilities. I think I’ll build a script to save every night for example a backup of config.js, custom.css, compliments.js and boot.txt (to compare in case of rebuild).
But, i’m also agree is represent a lot of work for a system that not modify every day. A big backup on every major modification is sufficient.
Have a nice day.