The Apache Configuration File & Building Apache

In the past, an advanced user who wanted to customize his Apache configuration had to directly edit the Apache configuration file (httpd.conf) on his web server. But with WHM’s AdvConfig system, editing the configuration file directly is no longer advised, nor do we believe it is necessary in most situations. The reasons for this change are as follows.

The Apache configuration file is not for data storage

The httpd.conf file is not meant to be used for data storage. Rather, it is a dynamically generated configuration file that our software modifies to make your websites accessible via a web browser. This file contains entries called “VirtualHost entries” that determine how a domain is configured; for example, whether it functions as an addon domain, parked domain, or subdomain.

This means that direct changes to httpd.conf are at risk of being overwritten by the cPanel and WHM software.

Important: If the configuration file is lost or corrupted, the state of a domain may be lost.

The Apache configuration file is not a configuration interface

The EasyApache interface allows you to configure Apache, rather than editing the httpd.conf directly. This is preferable, as the chances of creating a non-functional Apache configuration are significantly reduced when you use EasyApache's AdvConfig.

At times, cPanel software cannot be used to create a particular configuration. In these instances, it is possible to directly edit the Apache configuration file. However, it is generally not advised. We are swiftly moving away from the need to directly edit configuration files.

PHP and Apache should be fully configurable via EasyApache

One of the main goals of our software is to create an interface that allows you to fully customize Apache and PHP. Though the list of options may, at first, seem limited, they will cover the vast majority of circumstances.

EasyApache should create a working configuration

The number of configurations possible with EasyApache is nearly limitless; thus, creating a nonfunctional configuration by directly editing httpd.conf is a distinct possibility. With EasyApache, we have attempted to make the configuration process as straightforward and easy as possible.

Our interface will create a working configuration file in nearly all circumstances. However, if a working configuration cannot be created based upon your selections, our software will attempt to restore the previous working configuration and alert you of the issue, without making websites on your server inaccessible.