api service generally shown as inactive

[tpurschke]

find out why the api service is not active - do we actually need it? this is no functionality issue but might cause confusion with monitoring tools like zabbix

sudo systemctl status fworch-hasura-docker-api.service
○ fworch-hasura-docker-api.service - fworch API
     Loaded: loaded (/lib/systemd/system/fworch-hasura-docker-api.service; enabled; vendor preset>
     Active: inactive (dead) since Fri 2024-04-05 06:36:35 UTC; 5h 1min ago
    Process: 1302 ExecStartPre=/bin/sleep 10 (code=exited, status=0/SUCCESS)
    Process: 1333 ExecStart=/usr/bin/docker start fworch-api (code=exited, status=0/SUCCESS)
   Main PID: 1333 (code=exited, status=0/SUCCESS)
        CPU: 31ms

Apr 05 06:36:25 ubu22srv systemd[1]: Starting fworch API...
Apr 05 06:36:35 ubu22srv systemd[1]: Started fworch API.
Apr 05 06:36:35 ubu22srv fworch-api[1333]: fworch-api
Apr 05 06:36:35 ubu22srv systemd[1]: fworch-hasura-docker-api.service: Deactivated successfully.