MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    1. Home
    2. rmeskill
    3. Topics
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.
    R
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 15
    • Groups 0

    Topics

    • R

      Issues with pm2 in old mirror

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Troubleshooting
      4
      0 Votes
      4 Posts
      893 Views
      S
      @rmeskill hm… so, next guess is u uninstall pm2 and reinstall I think the command is pm2 u startup which will return the command to execute then to install again u can use my fixuppm2 script see https://github.com/sdetweil/MagicMirror_scripts
    • R

      Error on npm install

      Watching Ignoring Scheduled Pinned Locked Moved Solved Troubleshooting
      14
      0 Votes
      14 Posts
      8k Views
      R
      Seems my reply to this got lost… Got this working! Removed the .nvm directory, removed the symlinks, shutdown pm2 and re-ran the installation script and it all went in fine! sudo rm -rf ~/.nvm sudo rm -f /usr/local/bin/node sudo rm -f /usr/local/bin/nvm pm2 stop mm sudo rm -rf ~/MagicMirror bash -c "$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh)" I got an error on npm not being the right version, so upgraded that: sudo npm i -g npm (Note sudo is working now, which it wasn’t before) And now my node and npm versions look good and pm2 is running MagicMirror again! pi@raspberrypi:/ $ node -v v9.11.2 pi@raspberrypi:/ $ npm -v 6.5.0 Thanks everyone for the help!
    • R

      Versioning/maintaining changes?

      Watching Ignoring Scheduled Pinned Locked Moved Troubleshooting
      4
      0 Votes
      4 Posts
      2k Views
      T
      You could create a fork and have a branch within this repo referencing the original master branch. Using git different branches can have different remotes. (https://stackoverflow.com/questions/15775183/git-different-remote-for-each-branch). In this case if the master branch of the original project is updated you can pull these changes and merge them into your own fork’s branch. There could of course be merge conflicts which you would have to resolve. If you feel you have made changes which more people could benefit of, it would be easier to contact the original developer.
    • 1 / 1