Non helpful error message when started in clientonly mode about magicmirror

[tfischer4765]

But is it actually problematic? In my opinion, restrictions should not exist unless absolutely necessary. You might not see any use case right now, but somebody else might.

Look at my use case: I am running and will always run the frontend and backend on the same machine, but if I run them separately, I can change the config and restart the backend without the user even noticing the disruption, and much quicker too. There is no need to restart the frontend for a minimal config change.

My current workaround is to simply attach to the external IP of the device, but with what I currently know, I feel the restriction could be dropped completely with no ill effects whatsoever.

[tfischer4765]

Come to think about it: Is there a logical reason to block localhost? I stumbled upon it when trying to split my PM2 config into two, so I could restart the frontend and backend individually.

[sdetweil]

in general there is no need to use client on the same machine

just use a browser on the docker host

[sdetweil]

there is no guarantee that the front end will recover when the backend is restarted.

[tfischer4765]

I noticed that sometimes it will get out of sync. For my testing setup, that is no big issue. When I deploy it for real, I'll most likely go back to running it as a single task for now.

That still doesn't explain why localhost needs to be blocked in my mind, because it would be true whether you ran client and server on the same machine or on separate ones.

[sdetweil]

well, if you are going to run it on the same machine, then we recommend using the single instance execution

npm start
vs
npm run server
AND
npm run client