Grant_Bailey's questions

On my installation of CentOS 7, SELinux is enabled by default. This is preventing Apache from properly reading PHP files in the standard /var/www/html document root (the browser is blank when displaying web pages containing PHP script). When I disable SELinux the pages display normally.

Is there some way of setting SELinux to allow Apache to access PHP files from the document root? I would rather not disable SELinux entirely given that CentOS clearly believes it is a desirable security addition.

I've had to replace my server, the old one runs CentOS and the new one runs Debian.

In Debian, Apache has apache2.conf as its main configuration file with a number of others linked to it. In CentOS there is only one configuration file for Apache, httpd.conf.

Question: may I use the old httpd.conf file in the new server and if so, how do I ensure that the httpd.conf settings will prevail over the existing configuration files?

The post at Ubuntu Apache: httpd.conf or apache2.conf? indicates that the existing configuration files should not be changed in case of updates.

I realize that my custom configuration can be put into /etc/apache2/conf.d however, it is not clear to me whether the other configuration files in that location would conflict with it.