Closed andrewhowdencom closed 7 years ago
There is both a systemd service unit and a sysvinit bash script. I think ansible might be enabling the bash script somehow, by precedence.
Moving the sysvinit script out the way means the systemd service is enabled on boot. Just gonna try it the other way
Perhaps related: https://github.com/ansible/ansible/issues/22303
Potential workaround: https://github.com/ansible/ansible-modules-core/issues/3764#issuecomment-284331673
Might be resolved by https://github.com/geerlingguy/ansible-role-varnish/pull/65. Just testing.
Yah it worked. Using our fork for now -- if this gets merged in, awesome. <3
Thanks for the PR! I left a couple review notes.
Hola! Thanks for getting back to me. I've amended the review, and am running a test build now as a sanity check (though I have used this syntax previously).
As a design note, would you consider adding a .yamllint
file to the top of your repo? This would make code style nits such as EOL easier to catch in future
Booted fine
This is fixed via the merged PR now. Thanks!
Stub issue. I'm looking at this now, and will write what I find here for future people.