dc1b84fcfe
Everybody hates the local workers. The first step of getting rid of them is to split their socket out of osbuild-composer.socket - we need to keep this one to support the Weldr API but the local worker socket can live in its own file. The behaviour should be the same for now: osbuild-composer.service always starts the local worker socket. However, this split allows the osbuild-composer executable to be run without the Weldr API activated. The following commit explores this option more in depth. Note that the new socket can be used by root only because workers are always run as root. Signed-off-by: Ondřej Budai <ondrej@budai.cz> |
||
|---|---|---|
| .. | ||
| cloud-cleaner | ||
| osbuild-auth-tests | ||
| osbuild-composer | ||
| osbuild-composer-cli-tests | ||
| osbuild-dnf-json-tests | ||
| osbuild-image-tests | ||
| osbuild-koji | ||
| osbuild-koji-tests | ||
| osbuild-pipeline | ||
| osbuild-store-dump | ||
| osbuild-upload-aws | ||
| osbuild-upload-azure | ||
| osbuild-worker | ||