This systemctl command opens an editor to add an override file to the systemd service so the change is persistent because the next update will overwrite the systemd service file but the override.conf is kept.
Here is another example: Rsync to virtual host? - #3 by mrmarkuz
For SOGo:
Enter sogo environment:
runagent -m sogo1
Add the override.conf file:
systemctl --user edit sogo-app
Content of the override.conf file:
### Editing /home/sogo2/.config/systemd/user/sogo-app.service.d/override.conf
### Anything between here and the comment below will become the new contents of the file
[Service]
ExecStart=
ExecStart=/usr/bin/podman run --conmon-pidfile %t/sogo-app.pid \
--cidfile %t/sogo-app.ctr-id --cgroups=no-conmon \
--pod-id-file %t/sogo.pod-id --replace -d --name sogo-app \
--volume ./config/sogo.conf:/etc/sogo/sogo.conf:Z \
--volume ./config/cron-sogo:/etc/cron.d/cron-sogo:Z \
--volume ./config/sieve.creds:/etc/sogo/sieve.creds:Z \
--volume ./config/SOGo.conf:/etc/httpd/conf/extra/SOGo.conf:Z \
--volume ./backups:/etc/sogo/backups:Z \
--volume %S/state/custom_theme.js:/usr/lib/GNUstep/SOGo/WebServerResources/js/custom_theme.js:Z \
${SOGO_SERVER_IMAGE}
### Lines below this comment will be discarded
Check if the override file is appended:
systemctl --user cat sogo-app
Restart the sogo service:
systemctl --user restart sogo
The custom_theme.js
needs to be in /home/sogo1/.config/state/custom_theme.js
. Through the added volume it’s mapped to the container, so no need to copy it manually.
[sogo1@ns8rockytest state]$ ls custom_theme.js
custom_theme.js