Ah, so it’s still an HTTP call then, not a simple fileread from disk.

I saw that when I was fiddling with some other stuff, but never actually tested it. Is that path relative to the actual module location? Or MM’s installation? Or the user that’s running MM? So if '/foo/bar/baz' is defined, where does it start?

/foo/bar/baz? (OH PLEASE SAY NO, for the love of all that is sacred, tell me Node.js does NOT allow system reads like that!)
$HOME/foo/bar/baz ?
$HOME/MagicMirror/foo/bar/baz?
$HOME/MagicMirror/modules/foo/bar/baz?
$HOME/MagicMirror/modules/<MODULE>/foo/bar/baz?

@MichMich, I have a laser … let’s tie him up and put his hand under the beam. That’ll teach him!

@zombi27, yeah, @paviro wants to make sure that once you post your message, you are 100% committed to it. There will be no going back to change your post, or reply. You don’t get to pass GO and collect twice. :)

@paviro, but but but … @MichMich said … he said … he said node 6.1.0 is now supported. Dependencies be damned, they need to catch up.

That indicates you had an issue with your ID, which may not have been valid then.

I suppose that’s one way to do that … doesn’t make it very portable or sharable to others. It’s no longer contained within only MM and Node.js … But, if it’s working for you and does what you want, that’s the only thing that matters.

Got a reply on there at least. I don’t want the user to think we’re ignoring it.

@paulofernandesjr, you can install your monitor any which way you want, it’s your project to build and customize. If that’s the easier path to go, then by all means, go with it. Displaying MM on a regular monitor without a two-way mirror in front of that is perfectly fine. My development setup is exactly that, a 27" monitor rotated vertically sitting on my desk with an rPi connected to it. You can just as easy take a 7" Lilliput monitor and stick it ON an existing mirror.