For testing, it is useful to run setup-kolab in unattended mode.
There might be other reasons too, eg. as part of a docker setup etc.
One option is to use Puppet: Github: puppet-module-kolab. I don’t know enough about Puppet yet myself, and I have not tried it yet.
My way for an unattended setup is to patch setup-kolab in this way (see initSetupKolabPatches.sh to see the action in full context):
wget https://raw.githubusercontent.com/TBits/KolabScripts/Kolab3.3/kolab/patches/setupkolab_yes_quietBug2598.patch wget https://raw.githubusercontent.com/TBits/KolabScripts/Kolab3.3/kolab/patches/setupkolab_directory_manager_pwdBug2645.patch # different paths in debian and centOS # Debian pythonDistPackages=/usr/lib/python2.7/dist-packages if [ ! -d $pythonDistPackages ]; then # centOS6 pythonDistPackages=/usr/lib/python2.6/site-packages if [ ! -d $pythonDistPackages ]; then # centOS7 pythonDistPackages=/usr/lib/python2.7/site-packages fi fi patch -p1 -i setupkolab_yes_quietBug2598.patch -d $pythonDistPackages/pykolab patch -p1 -i setupkolab_directory_manager_pwdBug2645.patch -d $pythonDistPackages |
Now you can call setup-kolab this way:
echo 2 | setup-kolab --default --timezone=Europe/Brussels --directory-manager-pwd=test |
I need the echo 2 for the mysql options, that is a quick solution for the moment.
Unattended installation of Kolab