MMM-config with modules that have sub-configs (MMM-TouchButton)

sdetweil

i submitted this to the module

sdetweil

Tom added the schema file to the module package for future users

joey

Wow, that is great! I was just hoping for it to not reset the module settings. Being able to add the module-specific details is definitely useful. That you and Tom worked the rest of it out between my first post and now is even more amazing!

I set up my MagicMirror, but then leave it alone for a long time. I typically only touch it when an OS or MM update causes an issue. Looking back now, the entire setup process is so much better than it has ever been before!

Thank you for all the ways that MM has become easier and easier. (And thanks to Tom for adding the schema file!)

I meant to add a link to the module that started this discussion, since it has been useful to me: https://github.com/Tom-Hirschberger/MMM-TouchButton I mainly use it for shutdown/sleep/reboot functions, but it is a great way to be able to run an arbitrary command for an MM running on a touchscreen (or by opening the MM page from a different device and clicking the TouchButton).

sdetweil

@joey we are still discussing how to properly support his conditions settings, so there will be an update when we figure it out

the form library makes a lot of these things simple
add an enum to the string definition and now you get a select list, so a user cant put in the wrong thing, no spelling errors…

sdetweil

@joey make sure you backup, backup , backup

my backup/restore scripts on top of install/update
can give you a lot of security and safety

wishmaster270

@joey Great you like the module.
Just to clear out some things.

Most of the work did Sam not me. I only hit the merge button. So big thank you to him.

joey

@sdetweil said in MMM-config with modules that have sub-configs (MMM-TouchButton):

@joey make sure you backup, backup , backup

my backup/restore scripts on top of install/update
can give you a lot of security and safety

I should probably look into that. Currently, I just copy the entire directory to another place on the MM system (in case of an issue with upgrade or messing up the config), and I copy the config.js file to another system (in case of an OS/hardware issue – I use a LOT of old hardware). Up until now, I have mainly taken an OS/hardware failure as an opportunity to try a new flavor of Linux and investigate new modules while setting up MM from scratch again!

I am setting up a new one (brand new laptop with a manufacture date of only 12 years ago!) and it is a great opportunity to look into a proper backup with your scripts.

sdetweil

@joey the backup approach gives you the ability to restore the modules and config/css to another system , after install, so you get a migration tool

AND it provides git versioning… so if you need to go back 2 revs you can
it also supports putting the backup on a (private recommended) github repo, so you can restore directly from there and don’t have any local file system failure issues… disk drives, usb sticks, etc
AND it doesn’t matter WHERE you are at the time,