5b67a5947c
Right now the implementation expects the RCM socket to live in the same unit file as other osbuild-composer sockets. This would require a solution where we ship the osbuild-composer.socket in two different versions: one for regular usage, one for rcm. But that is very inconvenient and it would probably require some weird scriptlets (and scriptlets are bad!). After this change, the RCM API socket lives in a separate file and only if the socket unit is activated, the API runs. The unit file itself was introduced in previous commits. |
||
|---|---|---|
| .. | ||
| osbuild-composer | ||
| osbuild-dnf-json-tests | ||
| osbuild-pipeline | ||
| osbuild-tests | ||
| osbuild-upload-aws | ||
| osbuild-upload-azure | ||
| osbuild-worker | ||