I update the setup-Debian.yml task, so it ensures the Varnish services will be enabled on system boot.
When using service module I hit a bug [0], fixed a few days ago, but still on the devel branch. Because this bug, services are not enabled if the system has SysV and systemd configuration files, like Debian Jessie has.
Therefore, in the case of Debian Jessie, I make a workaround using the command module to call directly to systemctl.
I also update the installation steps following the current recomendations for Debian / Ubuntu on Varnish site [1][2].
These changes are:
Using HTTPS for the repo URL.
Because of 1, apt-transport-https must be installed.
The GPG key is unique for both distributions (The old URLs still works).
Debian and Ubuntu have different subdirectories in the repo (But, apparently, both have the same content).
I update the
setup-Debian.yml
task, so it ensures the Varnish services will be enabled on system boot.When using
service
module I hit a bug [0], fixed a few days ago, but still on the devel branch. Because this bug, services are not enabled if the system has SysV and systemd configuration files, like Debian Jessie has.Therefore, in the case of Debian Jessie, I make a workaround using the
command
module to call directly tosystemctl
.I also update the installation steps following the current recomendations for Debian / Ubuntu on Varnish site [1][2].
These changes are:
1
,apt-transport-https
must be installed.[0] https://github.com/ansible/ansible-modules-core/issues/3764 [1] https://varnish-cache.org/releases/install_debian.html#install-debian [2] https://varnish-cache.org/releases/install_ubuntu.html#install-ubuntu