Are you tired of editing config.js, or have trouble doing it, see my new module

[sdetweil]

@dinschal ah, I think that would be very difficult.

unless it was a text box w the same thing u would put in custom.css

[sdetweil]

@sdetweil one thing on position.

I write them out in the same order by
position:

all the top_left together, then the top_right, etc
using the module position order value, u can adjust the order of a module in a position list
( I add order: to the module info, so I can continue to keep them that way)

as mm shows them that way

they may NOT be in the same location( line number) in the new file

[Dinschal]

@sdetweil you got mail ;)

[sdetweil]

@dinschal I replied

[Dinschal]

@sdetweil yeah i have to search the right one :D

[Alyx]

Hi Sam,

I installed this just there on a fresh image and MM install. All good except my web-view is blank. Well the title comes up with the light brown background but there’s no content beyond that.

Do I need to begin installing other modules in tandem with this?

[sdetweil]

@alyx no… should work as is for the defaults…

let me look

[Alyx]

@sdetweil Sure what file/ image do you want to see?

[sdetweil]

@alyx hang on… let me test here… I am working on other fixes…

[Alyx]

@sdetweil no worries cheers buddy lemme know if you need anything

[sdetweil]

@alyx did you do the npm install in the module folder?? I need libs installed

http://mmip:mmport/modules/MMM-Config/review

I got

[Alyx]

@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

[Alyx]

@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
run npm fund for details

found 3 moderate severity vulnerabilities
run npm audit fix to fix them, or npm audit for details
smartmirror@smartmirror-ThinkCentre-M72e:~/MagicMirror/modules/MMM-Config$

[sdetweil]

@alyx ok, add debug:true

to my module def in config.js

(stop any pm2 version running, pm2 stop all)

then start MM like this
npm start >somefile.txt

there are all kinds of interesting problems with other modules, but none on the base that I know of.

send me the somefile.txt and the defaults. js from the MMM-Config folder… it is constructed from the modules installed

same userid as here at gmail

[sdetweil]

@alyx no… all useless messages we cannot do anything about

wait… is this windows?

[sdetweil]

@alyx said in Are you tired of editing config.js, or have trouble doing it, see my new module:

sudo npm install

NEVER EVER use sudo on any MM command…

delete my module folder and git clone and then npm install

[Alyx]

@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

[sdetweil]

@alyx but you used sudo, which messed things up… permissions as root when we need user level…

please delete my module folder, and reinstall without sudo…

you MAY have messed up the rest of the MM files too…

linux has very strict permissions

the postinstall failed which moves files to the right places…

[Alyx]

@sdetweil I used sudo because some package files reported back errors and that I dont have the required permissions?

[sdetweil]

@alyx probably cause you used sudo before…

so, I’d start over again… delete the MM folder

and run my install script, then add my module and npm install in its folder…