No description

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
cmd	Integration of osbuild composer with systemd	2019-10-02 17:56:59 +02:00
distribution	Integration of osbuild composer with systemd	2019-10-02 17:56:59 +02:00
internal	Integration of osbuild composer with systemd	2019-10-02 17:56:59 +02:00
tools	image-info: include output from rpm --verify	2019-10-01 17:05:10 +02:00
.gitignore	Add simple osbuild-worker	2019-09-26 23:58:03 +02:00
.travis.yml	minimal travis configuration	2019-09-24 17:50:48 +02:00
dnf-json	osbuild-composer	2019-09-13 18:50:13 +02:00
go.mod	Integration of osbuild composer with systemd	2019-10-02 17:56:59 +02:00
go.sum	Integration of osbuild composer with systemd	2019-10-02 17:56:59 +02:00
Makefile	Integration of osbuild composer with systemd	2019-10-02 17:56:59 +02:00