Does lilac work with docker/ansible
SolarAquarion opened this issue · comments
By "work with docker", do you mean that you have another distro other than Arch and want to run lilac inside an Arch container?
I don't understand what "work with ansible" would mean.
lilac doesn't have published docker image.
I don't understand what "work with ansible" would mean.
Ansible is https://www.ansible.com/ . Useful for multiple machine management.
lilac doesn't have ansible module or API.
BTW, why ansible?
Currently lilac can automatically run just by cron. No need to use ansible.
Do you need an automatic deployment?
I know what ansible is. I don't know why anything special needs to be done on lilac side to "work with ansible". It's just a normal cron job (or use systemd.timer, etc).
The question is I guess, is "What is the setup" of lilac and whatever on the build server's.
lilac will be packaged as an arch package also as a pypi package after #161 is solved.
For setup, copy config.ini.sample to config.ini. Also you may need to config a gpg key to sign the package and an ssh key to push commits to the repository on github.
There will probably need to be some documentation on how to spin up your own build server with lilac if wanted, but it can probably be just a build bot on your own server just as well.
I've updated the README file in this repo. It's not very detailed but I hope it helps.
One more question Concerning wine-tkg/linux-tkg https://github.com/Frogging-Family/linux-tkg and https://github.com/Frogging-Family/wine-tkg-git basically these PKGBUILD's and system turns 1 PKGBUILD into 10 different PKGBUILDS based on the configuration you chose. I don't think lilac supports the system of building PKGBUILD for each variation of it based on configurations you give in. Or can it be done via the yaml?
Well, you can create copies of it and build each variant you want in a subdirectory. lilac only supports one subdirectory with one devtools build command.
In my case, I want to run lilac in a container to increase security when building lots of AUR packages. It'll also be easier to setup on multiple nodes, and I don't want to use a VM for that.
There shouldn't be obstacles to run lilac in a container, as long as you setup lilac. I'm not good as writing Dockerfile though. Maybe I could try that when I have time, but maybe I won't have that time...