Read the statement by Michael Teeuw here.
-
@Jopyth said in [Remote-Control] Shutdown, Configure and Update your MagicMirror:
@AAPS (and everyone else): You can try the new version, but you can also go back to a previous version afterwards with the commands:
cd MagicMirror/modules/MMM-Remote-Control # or wherever you installed the Mirror and the module git checkout v1.0.0 # or the version you want
Currently, there is
v1.0.0
(which is probably the one you are on) andv1.1.0
as older versions. To check out the most recent version usegit checkout master
again.I want to update. But
git checkout master
does not work. There stands i shall usegit pull
but then there comes:
*Please, commit your changes or stash them before you can merge.
Aborting
* -
@fox Interesting. What changes did you make? I will try to give you a short
git
crash course for your case: You can get an overview viagit status
(should show changed files) andgit diff
(showing the changes themselves). If you do not care about these changes you should be able to usegit reset --hard origin/master
or if you do care about them usegit stash
, then dogit pull
, and thengit stash pop
to apply the changes again. -
@Jopyth said in [Remote-Control] Shutdown, Configure and Update your MagicMirror:
@fox Interesting. What changes did you make? I will try to give you a short
git
crash course for your case: You can get an overview viagit status
(should show changed files) andgit diff
(showing the changes themselves). If you do not care about these changes you should be able to usegit reset --hard origin/master
or if you do care about them usegit stash
, then dogit pull
, and thengit stash pop
to apply the changes again.Thank you!
What for a fantastic update! I tested nearly every module and everythink worked fine.
You refactored also the config file during saving. Awesome! Nice job. -
@Jopyth I forked your project and am looking into adding the functionality to toggle back and forth between different configurations with one click using the remote page (like having a set of different config files). Is this proposed change on your to do list as well?
-
Is there anything I need to do to update instead of just putting “git pull” in ~/MagicMirror/modules/MMM-Remote-Control ?
-
-
@Patex Do you want to do this with the
config.js
or with thesettings.json
(visibility of modules and brightness)? I had this idea once for the settings of visible modules and brightness, but did not implement it. Basically what other modules do with profiles defined in the config. I am not sure how much sense it makes to have multipleconfig.js
. One (large)config.js
(which includes all configured modules) and multiple “profiles” which only show a selection of these might be the way to go? -
@Jopyth What is the difference between develop and master version? Also, I probably sound dumb, but how do I change my ipWhitelist? Currently I have “::ffff:192.168.1.1/24” added. Do I need anything else? ( I would rather be able to access the mirror from any device )
-
Master branch is the official stable release
Developer branch is in development, so it contains new features but could contain bugs. Once the development team is happy they move the current development version over as the new stable release -
@AAPS If you want to allow all devices on your network, change the 24 to a 120 for IPv6:
::ffff:192.168.1.1/120
Also, new version with bugfixes is out, see below. Has anyone tried the installer yet? I made it mostly for fun, but I am still look for serious feedback. :)
[1.1.2] - 2017-02-01
Note: Since version 1.1.0 this module uses (new) dependencies, check the Updating section in the README.md.
Added
- Swedish translation
Changed
- Installation process updated in README.md
- Automatic installer/updater includes hint to restart Magic Mirror²
Fixed
- Issues with not applying shown and hidden status correctly to modules
- Issues where lockstrings were missing
- Modules sometimes did not show correctly in the UI as hidden or shown:
- This is due to a bug in Magic Mirror²
- PR #659 to fix this was made in the project, will be released in the next version