Seasoned developer here. Total n00b to OSS development.
I wanted to dip my toe in the water by sumbitting a PR to edit someone’s readme. It appears I don’t have write requests to the repo, which makes total sense… so how is this usually done?
Do I fork the whole repo and then request a merge or something?
Is there a guide somewhere?
I haven’t hard of some of those modules. hope you can post a picture soon.
@sdetweil pip is the python package manager
I also noticed that pip and pip3 instances are hogging the CPU. That can’t be good either!
I restarted, so I’m not sure why pip is running.
asking for help here! I’m a java dev, but now in management roles, so I don’t do this stuff as much. I can be a good contributor to the community, I just need a little help with getting off the ground, promise!
So I’m technical, but I don’t normally work with node.
How do I clean up this mess I’ve made for myself?
I started up node via npm and pm2 and noticed the system getting slower. Now, it’s unusable. I tried running htop to see what was running, and as I suspected, I started too many instances. Even after reboot, the instances seem keep running.
The screenshots below show. multiple instances of npm start, Daemon.js, node serveronly, npm, npm start, node /home/thelows/MagicMirror/node_modules/.bin/pm2 -
what’s a quick way to clean this all up, and … as a bonus, how should I start, stop, restart the MM process?
@davidgagne said in Raspberry Pi Zero W for Magic Mirror:
Summary
DISPLAY=:0 npm start I got an unexpected errorexport external_browser=firefox doesn’t this export vanish as soon as my session ends? Do I have to do this every time?Details:
When executing this script:
cd ~/MagicMirror export external_browser=firefox DISPLAY=:0 npm start
on this step: I get this output:
myname@raspberrypi:~ $ cd ~/MagicMirror
myname@raspberrypi:~/MagicMirror $ export external_browser=firefox
myname@raspberrypi:~/MagicMirror $ DISPLAY=:0 npm start
> magicmirror@2.27.0 start
> ./run-start.sh $1
./run-start.sh: line 79: 8050 Killed node serveronly
these are the lines that precede line 79:
# if user explicitly configured to run server only (no ui local)
# OR there is no xwindows running, so no support for browser graphics
if [ "$serveronly." == "$true." ] || [ "$xorg." == "." -a $mac != 'Darwin' -a "$wait_for_x." != "." ]; then
# start server mode,
node serveronly
else
# start the server in the background
# wait for server to be ready
# need bash for this
exec 3< <(node serveronly)
if we do export external_browser doesn’t that vanish as soon as the RPI is rebooted or if my session ends?
after a while the VNC client showed firefox start, but no URL, then the screen went white, then Firefox said “Unable to connect”
then I ran this script, I am tailing logs. What does “fix 'em up” script do
- Execute fix'em-up script:
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/fixuppm2.sh)"
the last line is this: pm2 setup completed - Fri Jun 14 21:52:48 PDT 2024
cancelling the step DISPLAY=:0 npm start allows me to rerun this step, but the step always ends in failure.
UPDATE: “Unable to connect” is because Firefox cannot connect to the node server. VNC can connect without issue! The error is actually an error from the Firefox browser.
@davidgagne It appears I need 1 reputation to upvote.
@davidgagne Wow, your summary above is just amazing! This is exactly what I was looking for.
Can you comment on why the choice of legacy OS was selected? Is there some kind of tradeoff that is being made here?