@htilburgs said in MMM-MyTasklist:

Is there a tule for the Ports? Which I can use or not use?

you could add a config param for the port so that everyone who collides with 8123 could choose another one without hacking the source code

@KristjanESPERANTO

AFAIS the wrong license is coming from the gitHubData.json file.

So looking into https://github.com/MagicMirrorOrg/MagicMirror-3rd-Party-Modules/blob/main/scripts/updateGitHubApiData.js I stumbled over the line
let maxQueryCount = 58; which is used in the shouldFetch function.

Maybe I’m wrong but this looks like we only fetch 58 repos from github and then switch to historical data?

@sdetweil

only wanted to post this variant …

As background: This is a feature of my docker container where you can use a config.js.template and the variables are defined in the docker-compose.yml which starts the container and before starting mm I run envsubst to make the real config.js.

@tonyarogers said in MagicMirror problem:

Network service crashed

I had similar problems with a setup on a pi zero 2w.

The pi 3A+ seems to have the same memory of only 512 MB.

Short story: The os and the dependencies of mm (node and electron) seems to need more memory with every new version. I gave up with such hardware.

It is not impossible to get it running with increasing swap size or using 32-bit os but it is a dead end …

you can put this into css/custom.css file:

.newsfeed-desc {
  display: none;
}

@KristjanESPERANTO

Thanks! Maybe I take a look into the authenticating stuff …

@wmx

should be

icons: [{
  "default": "http://localhost:8080/cors?url=http://<my-ha-url>:8123/local/images/hem.png"
}]

@parnic

bullseye support ends in 5 month. But I don’t think we will remove the x11 start option because there are many other os which have no wayland support.

This is an electron option, wayland needs an extra param -ozone-platform=wayland. This is all defined in the package.json.

So as long as electron supports x11 I see no reason to remove the x11 option from mm.

With the new release we only switched to wayland as default option (when you use node --run start) because we think the majority is meanwhile using wayland.

@majorc said in Cursor shown in v2.16.0:

Or do I have to wait for version 17?

In v2.16.0 we have electron v11, in current develop branch (which will become v2.17.0 in October) we have upgraded to electron v13.

see https://github.com/MagicMirrorOrg/MagicMirror-3rd-Party-Modules/pull/65

@sdetweil

the docker image karsten13/magicmirror:latest doesn’t contain python. Simplest solution for this is to use the fat image karsten13/magicmirror:fat, for more infos: https://khassel.gitlab.io/magicmirror/images/

https://forum.magicmirror.builders/topic/12815/bright-ui?page=1

https://forum.magicmirror.builders/topic/13108/css-experiments-for-newbies

which raspberry pi os did you install?

It must be one with desktop

@HeikoGr

Thanks! Your configuration inspired me to write down and update my own.

I don’t mean to hijack your thread, but since development environments are always a matter of personal preference, I thought I’d share this as an alternative.

@sdetweil said:

the custom*.css files get moved

no, only css/custom.css and only if the target specified in config.customCss doesn’t exist.

This is the normal setup used by ~95% of the users, we cannot handle every edge case so these users must change it manually.

@BKeyport said:

I’m currently setting the CSS file with customCss: “css/custom3.css”, in the config,

I’ll change that to customCss: “config/custom3.css”, ?

in your setup no file is moved automatically. As you are already using the config.customCss feature you can do the changes before next release by

• move all the custom*.css file from css to config
• change config.customCss: "config/custom3.css"

@sdetweil

yes, the docs … no native english speaker so docs are always a struggle. Thanks for the hints, will update …

@dorianhawkmoon

you can run

MM_CONFIG_FILE=config/config.js npm run server

and

MM_CONFIG_FILE=config/config2.js npm run server

Same works for npm run start.

You have to use different ports in your configs.

@sdetweil said in Running on Pi Zero 2 W?:

as addition: pi zero 2 is armv7l

nice article: https://blog.alexellis.io/raspberry-pi-zero-2/

@kayakbabe

it is a good idea to put the compliments.json beside the config.js.

In the config.js you have to use

remoteFile: "../../../config/compliments.json"`

@mumblebaj

you can test the following, I couldn’t test this completely but the cors error was gone in my tests.

First yo need to create own certs, go into the config folder of mm (same folder where config.js is located) and run this command:

openssl req -newkey rsa:4096 \
            -x509 \
            -sha256 \
            -days 3650 \
            -nodes \
            -out example.crt \
            -keyout example.key \
            -subj "/C=DE/ST=Hessen/L=Frankfurt/O=MagicMirror/OU=MM/CN=www.example.com"

Then edit your config.js and add the following lines under the line with var config = {

	electronOptions: {
		webPreferences: {
			webSecurity: false
		}
	},
	useHttps: true,
	httpsPrivateKey: "config/example.key",
	httpsCertificate: "config/example.crt",

(Re)Start mm and test if MMM-Hue works now (there will still be a “mixed content” warning).