Skip to content
Riversoft STCP Gemini
Operation

Operation

The Riversoft® STCP Gemini API and Riversoft STCP Gemini Server can run as services managed by systemd or directly from the command line.

Services

Componentsystemd service
Riversoft STCP Gemini API (includes the Portal)stcpgemini-api
Riversoft STCP Gemini Serverstcpgemini-server
systemctl start stcpgemini-api
systemctl start stcpgemini-server

Check that the status shows running:

systemctl status stcpgemini-api
systemctl status stcpgemini-server

Start the API before the Server. The Server needs an instance created in the Portal.

Command line

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

Riversoft STCP Gemini API 

stcprestapi -lite -p 33070 \
  -config /usr/local/stcpgemini-api/configs/config.json \
  -webapp /usr/local/stcpgemini-api/portal/app \
  -c <certificate> -k <private-key>

In test environments without TLS, replace -c and -k with -ns.

With -lite, the API itself serves the Portal files. All options are in the Command reference.

Warning

Choose between disabling TLS (-ns) or enabling it with -c and -k together. Do not combine -ns with -c/-k.

Riversoft STCP Gemini Server 

/usr/local/bin/stcpserver /usr/local/stcp/configs/stcpserver.config.json

The stcpserver options override the equivalent configuration file parameters. See the Command reference.

Containers

  • Keep the process in the foreground so the orchestrator (Docker, Kubernetes, etc.) can track the container lifecycle.
  • Do not force Riversoft STCP Gemini Server daemon mode (-F).
  • Install Riversoft STCP Gemini Rename in the same image as Riversoft STCP Gemini Server when using routing.
  • Use the API -init-db and -init-db-file options only during the initial installation, never in normal execution.
AdministrationAuditing