modules

sdetweil

@pat59 I know. But if you keep changing we can’t debug what’s going on

There had to be at least one message for bolster in the startup messages.

pat59

@sdetweil Hello, yes, I understand perfectly. Excuse me, being a novice, I’m too afraid I won’t be able to get it working again. I’ve put the old module back in. I’m going to try again with MPlayer and will get back to you. Once again, I’m sorry, I’m very attached to my mirror.

sdetweil

@pat59 I understand. I suggest using a new separate config file for new individual modules until you get them working

You can use the environment variable to define it

export MM_CONFIG_FILE=config/fribble.js
Or whatever name you choose
Then
npm start
After turning off any pm2 instance
Then you haven’t touched your good config
Can stop any time, have only one module of output to deal with

Once all good, you copy this one module def to your good config

pat59

Hello,
Sorry to be back, I had to be away. I’m taking this opportunity to ask you to close the request as I’m currently unable to address the issue. Thank you for your understanding.

Sincerely,
I would like to thank everyone who contributed. See you soon.

sdetweil

@pat59 no problem leaving it open. Come back when you can.