Mint is also Debian based so the recommendation is to use the script I linked to, and use systemd to run it. The script will automatically set that up.
As I said, you should be able to run journalctl in an exec node. Set it to Spawn mode so it outputs the log on the fly.
I dont think you can put pm2's managed app logs in a systemd's journal. Maybe you should create your systemd service definition file.
After googling i discovered that pm2 generates a systemd doc that manages its own process using systemd, not the app's. That is probably the reason you can't see app logs using journals.
Pm2 logs doc page PM2 - Logs
Not really sure why you want to use PM2 when running on Linux and certainly not for a "production" setup. I only use it on Windows for a dev setup that isn't always running (well, actually it now kind of is always on since I start it automatically a few seconds after logging into my usual desktop user).
Run it with systemd instead and the logs will already be using the journal. And you can do most of what you might want with PM2. The only possible exception being auto-restart on watched file changes.
Don't forget there is a command node-red-log, a bash script, which reads the Node-red logs (using journalctl) - assuming you are on Debian and installed with the official script.
To start Node-red on boot it's sudo systemctl enable node-red
Edit: oops!
To start Node-red on boot it's sudo systemctl enable nodered
I do wish whoever invented 'Node-red' hadn't used that hyphen!
Yor're right. I always read manuals but sometimes the reading is a bit too fast (like skipping all ridiculous and unnecessary safety warnings)... In this case I guess I stopped reading that sentence at "Raspberry"...
Somewhere in the back of my head, there is a memory of the Raspberry install script is installing a way older version of Node-RED than the npm install but this is not the case today where both install methods install ver 4.1.0.
That has never been the case. Possibly you are thinking of the situation if node-red is installed from the OS repositories, which will almost always be out of date, if it is present. For example, Debian Bullseye on the pi currently has v2.2.3 available for install.
