A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
Read the statement by Michael Teeuw here.
MMM-Fritz-Box-Callmonitor: Notification formatting
-
@rabbit83ka you can set the venv in the mm.sh that starts MagicMirror
then you don’t need to do that
-
@sdetweil Thanks, so it should look like this?
#!/bin/bash # This file is still here to keep PM2 working on older installations. cd ~/MagicMirror export PYTHONPATH="/home/pi/venv/bin/python" DISPLAY=:0 npm start
-
@rabbit83ka no, execute the venv command to set the virtual environment in place of the export
the same venv command you did before running pip
-
@sdetweil I used your script
fixuppm2.sh
when I set up the mirror
Now I modified ~/MagicMirror/installers/mm.sh to#!/bin/bash # This file is still here to keep PM2 working on older installations. cd ~/MagicMirror source venv/bin/activate DISPLAY=:0 npm start
but that doesn’t work, error occures again because node_helper doesn’t seem to use the venv.
-
@rabbit83ka when I look at my .bashrc whichs sets up the default venv on shell open
I see# Virtual Environment Wrapper source /usr/local/bin/virtualenvwrapper.sh PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig export PKG_CONFIG_PATH cd ~
this topic seems applicable
https://unix.stackexchange.com/questions/87062/how-to-display-the-name-of-the-current-virtualenv -
@rabbit83ka I also see this for background