# RFC: remove apache2\_module

**URL:** <https://forum.ansible.com/t/rfc-remove-apache2-module/17278>\
**Category:** Ansible Developer\
**Created:** [January 15, 2015, 1:22pm UTC](https://forum.ansible.com/t/rfc-remove-apache2-module/17278 "2015-01-15T13:22:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rene\_Moser](https://avatars.discourse-cdn.com/v4/letter/r/7bcc69/32.png) [@Rene\_Moser](https://forum.ansible.com/u/Rene_Moser)\
**Post date:** [January 15, 2015, 1:22pm UTC](https://forum.ansible.com/t/rfc-remove-apache2-module/17278/1 "2015-01-15T13:22:46Z")

</div>

Hi

I want to start a discussion whether the core module **apache2\_module** should be removed or not, or be moved to extra

**Why I vote to remove:**

1. The functionality of this module is limited to Debian OS family. (does a2enmod exists somewhere else?)
2. The functionality can be easily replaced with command module:

command: a2enmod {{ item }} creates=/etc/apache2/mods-enabled/{{ item }}.conf  
with\_items: modules\_enabled

command: a2dismod {{ item }} removes=/etc/apache2/mods-enabled/{{ item }}.conf  
with\_items: modules\_disabled

1. Less code, less bugs, less time for maintenance.

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [January 15, 2015, 2:48pm UTC](https://forum.ansible.com/t/rfc-remove-apache2-module/17278/2 "2015-01-15T14:48:03Z")

</div>

It seems that the Suse folks also include these, but with slight  
differences in output.

---

<div class="post-metadata">

**Author:** ![mcv21](https://avatars.discourse-cdn.com/v4/letter/m/7bcc69/32.png) [@mcv21](https://forum.ansible.com/u/mcv21)\
**Post date:** [January 15, 2015, 6:52pm UTC](https://forum.ansible.com/t/rfc-remove-apache2-module/17278/3 "2015-01-15T18:52:06Z")

</div>

Hi,

> I want to start a discussion whether the core module\*apache2\_module\*  
> should be removed or not, or be moved to extra

I strongly think not. It's a very useful module, is hardly a vast pile  
of code to maintain, and means that we don't have to care about exactly  
where enabled modules are kept (since a2{en,dis}mod do that for us).

> 1. The functionality of this module is limited to Debian OS family.  
> (does a2enmod exists somewhere else?)

SLES also has it, and what that version does is not the same as your  
command-suggestion assumes - instead it changes entries in  
/etc/sysconfig/apache2.

Regards,

Matthew