@sdetweil sent back over
Read the statement by Michael Teeuw here.
Posts made by Alyx
-
RE: Are you tired of editing config.js, or have trouble doing it, see my new module
@sdetweil
Did the debug what folder does it go to? I have the somefile ready alsoAs for the messages I get the first part but not the second saying its created
-
RE: Are you tired of editing config.js, or have trouble doing it, see my new module
So I’m experiencing a new issue where when I use the editor and trhen press save its not actually saving the new co’ve reinstallked the module and even chmod the folder to 777
Is this an issue others are experiencing?
I have the config for it on the defualt settings and the somefile.txt reports that everything is find and it opened successfully on port 8301 ( this seems to change actually) I’m thinking that the port is changing while I’m editing?
-
RE: Are you tired of editing config.js, or have trouble doing it, see my new module
@sdetweil ok I flash reinstalled MM (worryingly good at it now…) and it seems to be working :)
The config pops up on the webpage correctly and all.
Thanks Sam!
-
RE: Are you tired of editing config.js, or have trouble doing it, see my new module
@sdetweil I used sudo because some package files reported back errors and that I dont have the required permissions?
-
RE: Are you tired of editing config.js, or have trouble doing it, see my new module
@sdetweil So I did as you said and the npm run is stuck loading for a while and the text file is empty.
Now I’m running in server mode if that matters? I used npm run server >somefile.txt
-
RE: Are you tired of editing config.js, or have trouble doing it, see my new module
@alyx actually i had a harder look, does this seem important?
smartmirror@smartmirror-ThinkCentre-M72e:~/MagicMirror/modules/MMM-Config$ sudo npm install
npm WARN lifecycle mmm-config@1.0.0~postinstall: cannot run in wd mmm-config@1.0.0 node exec_script.js ./postinstall:postinstall.cmd (wd=/home/smartmirror/MagicMirror/modules/MMM-Config)
npm WARN mmm-config@1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})audited 136 packages in 1.22s
7 packages are looking for funding
runnpm fund
for detailsfound 3 moderate severity vulnerabilities
runnpm audit fix
to fix them, ornpm audit
for details
smartmirror@smartmirror-ThinkCentre-M72e:~/MagicMirror/modules/MMM-Config$ -
RE: Are you tired of editing config.js, or have trouble doing it, see my new module
@sdetweil Yep I did it within the MMM-Config directory, did it again there with no luck. Got some audit issues for npm but nothing big
-
RE: Are you tired of editing config.js, or have trouble doing it, see my new module
@sdetweil no worries cheers buddy lemme know if you need anything