Operation

Riversoft® STCP DirectLink can run as a service managed by systemd or directly from the command line. How users work with the portal is described in Using Riversoft STCP DirectLink Portal.

Services

systemctl start stcpgemini-api
systemctl start stcpdirectlink

Check that the status shows running:

systemctl status stcpgemini-api
systemctl status stcpdirectlink

Riversoft STCP DirectLink uses the instance created in the Riversoft Console Portal, set in cfgInstanceName (see Configuration).

Command line

Running from the command line is useful for tests and in containers, where the process must run in the foreground as the main process.

Riversoft STCP DirectLink

/usr/local/bin/stcpdirectlink \
  -noService \
  -config /usr/local/stcpdirectlink/configs/config.json \
  -lang ptb \
  -langfile /usr/local/stcpdirectlink/configs/messages.json

With -noService, the process runs in the foreground. All options are in Running and installing the service.

Riversoft STCP Gemini API

Running the API from the command line is described in Riversoft STCP Gemini operation.

Containers

• Keep the process in the foreground, with -noService, so the orchestrator (Docker, Kubernetes, etc.) can track the container lifecycle.
• Do not use -installService in containers. On Linux, the service is created by the package, and -installService is used only on Windows.
• Keep config.json and secrets out of the image: mount them as a volume or use a secrets provider (see KMS and secrets).