How Node.js apps work
Most sites never need this. It exists for the thing WordPress hosting usually pushes onto a second bill: a small API, a webhook receiver, a background worker.
It runs in the same container, on the memory and vCPU you already pay for. To set one up, see deploy a Node.js app.
What this can’t do
The screen doesn't show whether your app is running — no status, no uptime, no restart button.
What to do: read the log, and refresh it — new output means the app is alive. For certainty, have the app log on a timer or answer a health path you can open in a browser.
Automatic is a restart policy, not a status. It means "restart this if it exits", not "this is up".
What to do: treat it as an instruction to the platform and check the log for the truth.
The log is a plain tail of stdout and stderr — no paging, no history, no clearing.
What to do: write your own log file inside the app for anything you need to keep, and read it over SSH.
Restarting the app means restarting the container.
What to do: press Restart on your Pressy's overview, and expect a few seconds of downtime on the website too.
Didn’t solve it?
Write to us with your Pressy’s address and what you were doing when it went wrong. Answered by the people who built it.
Last updated