Hi I'm using the geerlingguy.apache role to deploy apache, in my case onto Ubuntu 16.04. This works great. The machine needs to run a custom build apache module, but I'm not sure what the best way is to order things.
The apache role takes care of enabling modules, and also the vhost config - which includes module specific statements. If I want to use that then obviously the module first has to exist. So I first run a playbook to compile my module. The resulting module definition should go into /etc/apache2/mod-available/mymodule.load - which doesn't exist. It's a bit of a chicken/egg situation. I could just create /etc/apache2/mods-available/mymodule.load in the first playbook, so that the apache role can find it, but that seems dodgy. Or is this not a problem? Thanks! Dick Visser -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAEQQDNnd2ACDwWx4hB7raVBU144MsDkfHfbAOTnOSHdoc9YwMw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
