In reply to @c0ba1t:matrix.org
Maybe? You have only posted an excerpt from an NGINX vhost config with an `example.com` domain and a systemd unit.

In reply to @peter-lustig:matrix.org
the systemd service

In reply to @c0ba1t:matrix.org

In reply to peter-lustig
the systemd service

If your app logs to stderr/stdout, you might want to look into the journal (journalctl -xeu ) to inspect your app logs

Here is my current systemd service:

systemd.services.myservice = {
    wantedBy = ["multi-user.target"];
    after = ["network-online.target"];
    serviceConfig = {
      Type = "simple";
      ExecStart = "PORT=5173 ${pkgs.nodejs_20}/bin/node .";
      WorkingDirectory = inputs.myservice.packages.${pkgs.system}.default;
      Restart = "always";
    };
  };

In reply to @lily:lily.flowers
PORT=5173 is not a command

it is just a command line

from the docs:

PORT, HOST and SOCKET_PATHpermalink
By default, the server will accept connections on 0.0.0.0 using port 3000. These can be customised with the PORT and HOST environment variables:

HOST=127.0.0.1 PORT=4000 node build
Alternatively, the server can be configured to accept connections on a specified socket path. When this is done using the SOCKET_PATH environment variable, the HOST and PORT environment variables will be disregarded.

SOCKET_PATH=/tmp/socket node build

In reply to @lily:lily.flowers
PORT=5173 is not a command

it is just a command line argument

from the docs:

PORT, HOST and SOCKET_PATHpermalink
By default, the server will accept connections on 0.0.0.0 using port 3000. These can be customised with the PORT and HOST environment variables:

HOST=127.0.0.1 PORT=4000 node build
Alternatively, the server can be configured to accept connections on a specified socket path. When this is done using the SOCKET_PATH environment variable, the HOST and PORT environment variables will be disregarded.

SOCKET_PATH=/tmp/socket node build