@sdetweil said in global variables in config.js:

@Sean “24” means not am/pm, and it shows seconds ticking…

That is my point. Each value could have a different meaning in different modules. I can’t use MM-level-global-timeFormat in calendar and clock modules which are created by me because that value is too ambiguous and has a meaning only in default calendar/clock modules. But If timeFormat would become the definite global value,(well, frankly it is already) the user will expect it works also in my modules like default module. But I can’t.
How about location? Some of the default weather-related-modules are using it like location: "New York", but other Geo-information-related-modules might need another format of value as that kind. If it could not be used really GLOBALLY, how it could become really useful?

This clock suitable for outdoor? What is the best projection clock with outdoor temperature? Like in this article Best Projection Clock with Outdoor Temperature | Webproductradar

@siggmur eaddr in use means something is still using that port 8080,

pm2’s job is to start at boot, so you can have more than one running

keep stopping

check w
ps -ef | grep node |grep -v grep

kill things til u get none.

then

cd ~/MagicMirror npm start