@bicolorbore586 very first line of the file, all by itself
Before any comments
Read the statement by Michael Teeuw here.
Posts
-
RE: MMM-CalendarExt3
-
RE: MMM-CalendarExt3
@bicolorbore586 add this to the top of config.js, very first line
var document;
I’ll open a bug report
I opened https://github.com/MagicMirrorOrg/MagicMirror/issues/3990 -
RE: MMM-CalendarExt3
@bicolorbore586 can you do
cd ~/MagicMirror npm run config:checkdoes it produce the same error?
also donode -c config/config.jsif it returns and displays nothing, then node did not detect any syntax errors.
edit: I can reproduce this
-
RE: MMM-Chores - Manage and keep track of your household Chores
@ewingfox please always code block for code, config and logs
paste the text into the message editor window, blank line above and below
select the text just pasted
hit the </> button on the message editor toolbarI fixed prior
-
RE: Using different configs
@chrga yeh, page is a client thing not server,
Client connects and server sends index.html like any other web server
May be browser cache issues if the page changes on the same url, we don’t have a page expiry setting on the urlAgain two configs on same port is fine if shutdown/startup
Two configs loaded on two instances on different ports is fine
Client has to request a different url -
RE: Using different configs
@chrga server is where the configs work. client doesn’t know anything except the port number , which MUST be different if both run at the same time.
-
RE: Using different configs
@chrga you could use MMM-pages to define two logical ‘hidden’ pages, and use notifications to switch between them
only one config…MM can only show or hide content… but the grouping of visible content defines a ‘logical’ page…
-
RE: Script seems to be failing
@ankonaskiff17 thanks… got the log, it shows installing the right nodejs version,
BUT the check returns the old… SO…
I didn’t see what pi this was on? 4/5?
i can retest here… -
RE: Script seems to be failing
@ankonaskiff17 said in Script seems to be failing:
tar: bin: Directory renamed before its status could be extracted
all the search lists that error as mostly occurring on docker…and a known file system error
is this a docker container??