Birmingham mumbai

[
 358 
]
Chances are, though, if you've installed a package for an additional module, it was 
most likely was enabled for you during installation. With Debian and Ubuntu, it's 
very common for daemons and modules to be enabled as soon as their packages 
are installed, and Apache is no exception. In the case of the 
libapache2-mod-php7.4
 
package I used as an example, the module should've been enabled for you once the 
package was installed:
sudo a2enmod php7.4
If a module is already enabled, you will see output similar to the following when you 
try to enable it with 
a2enmod
:
Module php7.4 already enabled 
If the module wasn't already enabled, we would see the following output:
Enabling module php7.4. 
To activate the new configuration, you need to run: 
systemctl restart apache2
As instructed, we'll need to restart Apache in order for the enabling of a module to 
take effect. Keep in mind, restarting Apache will make any sites it may host become 
unavailable during the process. When it comes to disabling a module, the command 
syntax is fairly similar. To do so, you'll use the 
a2dismod
 command along with the 
name of the module you'd like to disable:
sudo a2dismod php7.4
Enabling a module that was already previously enabled will result in output similar 
to the following:
Module php7.4 disabled. 
To activate the new configuration, you need to run: 
systemctl restart apache2
The modules you install and enable on your Apache server will depend on the needs 
of your website. For example, if you're going to need support for Python, you'll 
want to install the 
libapache2-mod-python
 package. If you're installing a third-party 
package, such as WordPress or Drupal, you'll want to refer to the documentation 
for those packages in order to obtain a list of which modules are required for the 
solution to install and run properly. Once you have such a list, you'll know which 
packages you'll need to install and which modules to enable.

---

Chapter 14