debian-forge-composer/distribution/osbuild-composer.socket
Martin Sehnoutka ed185b41ce Integration of osbuild composer with systemd
osbuild-composer now uses socket activation instead of hardcoded paths
in the code. osbuild-worker is an http client therefore it uses only
service unit. osbuild-worker must be started after the socket is
created. osbuild-composer service requires osbuild-worker to run, because without
it no jobs can be started.

osbuild-composer is executed as a regular user (newly created
_osbuild-composer user) as opposed to the worker which must run as root
in order to execute osbuild itself
2019-10-02 17:56:59 +02:00

9 lines
165 B
SYSTEMD

[Unit]
PartOf=osbuild-composer.service
[Socket]
ListenStream=/run/weldr/api.socket
ListenStream=/run/osbuild-composer/job.socket
[Install]
WantedBy=sockets.target