Read the statement by Michael Teeuw here.
Questions about update
-
@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 beginerSample 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!
Impressive :)
-
@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?
-
@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
? -
@karsten13 Make all things like me after you can talk ;)
-
Hi,
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.
-
@bkeyport thanks. my backup doesn’t copy custom.css… doah
-
Just scripted what I want. Not externalized for the moment. Just a simple copy of modules folder and personnalized files.
Sorry if it’s not perfect, but i’m not a developer :)
#!/bin/bash #BACKUP FOLDER mkdir -p /var/backups/MM cd /var/backups/MM #OLD BACKUPS PURGE echo "--- PURGE TASK ---" echo "Check for existing backups..." nb_save=$(ls | wc -l) if [ $nb_save -gt 4 ] then oldest_folder=$(ls -lt | tail -1 | cut -d " " -f10) echo "Limit of 5 backups reach. Deleting of the oldest one : $oldest_folder" rm -rf "$oldest_folder" echo "DELETED." else echo "Limit of 5 backups doesn't reach, skip to backup task." fi #BACKUP echo "--- BACKUP TASK ---" echo "Starting..." d=$(date +%Y-%m-%d_%H:%M) mkdir -p $d cd $d cp /home/pi/MagicMirror/config/config.js config.js cp /home/pi/MagicMirror/css/custom.css custom.css cp /home/pi/MagicMirror/modules/default/compliments/compliments.json compliments.json cp /boot/config.txt config.txt mkdir -p modules cp -R /home/pi/MagicMirror/modules/ . echo "DONE. CURRENT LIST OF BACKUPS :" cd .. ls -A1
-
@selyjohns cool… mine saves the list of modules (git url) and config.js to a local git repo with a tag with the date
other files (compliments.json) … cool… (any reason u didn’t put those in config.js?, u have to restart to use an updated file too)
-
@sdetweil said in Questions about update:
@selyjohns cool… mine saves the list of modules (git url) and config.js to a local git repo with a tag with the date
Perfect :) Git seem to be a good solution. For next evolution haha
For the json, it’s because i’ve define a lot of compliments and it’s more clean on external json that in config.js