Managing Applications

All the applications that Momod installs are controlled via systemd service units and the standard systemctl start, stop etc commands.

For those applications running directly on the host status can be checked by a server Admin user, but both Forgejo (as installed by Momod) and Syncthing are slightly special cases:

# For Forgejo
systemctl status gitea

# For Syncthing
systemctl status syncthing@syncthing

The admin user will need to use sudo to stop or start these services:

# For Forgejo
systemctl stop gitea

# For Syncthing
systemctl stop syncthing@syncthing

Managing rootless Podman application services

Admin tasks for rootless containers must be carried out as the user running the service. Each service has it’s own user, so you must first switch to that user account then use the ‘–user’ flag to systemctl. There is an added layer for some applications because they’re running in a rootless Podman pod.

For example, Miniflux, which runs in a Podman Pod with it’s database:

sudo su - miniflux
systemctl --user stop pod-miniflux

Would stop both the Miniflux container and it’s database service. You can also just act on a container running within the pod:

sudo su - miniflux
systemctl --user restart container-miniflux-app

Not all apps are in pods, eg Radicale:

sudo su - radicale
systemctl status container-radicale

Knowing exactly which service name to use can thus be a little complicated. The best way is to look at the roles/app_appname/templates directory in the Momod source to see which service file templates are uploaded to the server.

The following Podman commands can also be helpful to show which if any pods and containers are currently running:

sudo su - vikunja
podman pod ps
podman ps