Finally, after a couple of dozen (approximately on Friday) attempts to launch a managed server in Dart, it started working as it should.

The stack ended up like this: docker + pm2 + dart (serverpod) docker - for PostgreSQL pm2 - for managing the serverpod server instance serverpod - the actual server 
The words and meanings are all mixed up, but it's a start:)
Several criteria were important:
- easy to start | stop
- easy to monitor the instance status
- configure it so that the server could reach the database on its own - this turned out to be a non-trivial task

I tried the several options:

Put it in Docker, run it in Docker via cmd, but here's the catch - since Postgre is in another container, you need to link the containers through a network. And there are a million nuances right away: specifically, serverpod has one config for everything at once - which is convenient and inconvenient because in the end you need to map the ports differently. In the end, I spent two days on this option and decided to discard it.

Then I moved to pm2, since it's very convenient in pm2 to monitor and start the running instances, but it didn't work out right away either, for example, it turned out to be easier to start via a terminal command than through a config.

An alternative to pm2 is standard Jobs in Linux, but Dart was constantly crashing in them.

Like the hashtag