hi, my situation is this: i’ve an express server app running successfully on balena OS on a port other than 80, which is used by the default balena app (
usr/src/app/server.js). my server continues running even if i close the web console window but i no longer have access (obviously) to its output even if create a new web console. i can’t start my app at boot. i can’t log its output (i don’t want to write to and ruin the SD card). i can only access my express server locally, not at the public URL. i cannot integrate my code into the default express app – it crashes (see below). my app requires node modules that need compilation, e.g. sharp, and therefore i must first run
apt-get g++ and
apt-get make) on balena OS.
also, killing the default express server (
kill -9 xx) causes ALL web console and web log screens to disconnect (all that are open) & reconnect. is there a reason for this? is this normal behavior?
modifying the default app ("
/usr/src/app) with our code causes repeated disconnects and reconnects. i don’t want to mess with it as we can get locked out; we are currently not able to
ssh to the main OS using
balena ssh – there’s some issue there (on a separate thread on this forum).
pm2 on my other web appliances to run and manage express – startup, logs, restart on crash, etc. it provides amazing control.