Download apache web server for fedora how to#

All files should be read-only, unless explicit permissions allow otherwise. Each application will be segregated into its own child app directory. This directory contains web application directories, which host the application files. IвЂ™m only showing a subset of directories and files, but it should be enough for the purposes of this tutorial. Our application has the following directory tree on the web server. Your structure will more than likely differ due to environmental requirements. Application Directory StructureД«efore designing an SELinux policy for our web application, we need to understand the directory structure our application will use.

Download apache web server for fedora how to#

The scope is to show how to apply common Apache SELinux contexts to a web applicationвЂ™s directory structure, by creating and applying custom policies, allowing you to place your files outside of the default location (/var/www/html). This tutorial assumes that MySQL and Apache are already installed and configured.

Some directories require write access for uploading content.

Some files require for the application read and write access.

SELinux blocks Apache from loading content outside of default directories.

Application must reside outside of the default Apache directory (/var/www/html).

Aside from allowing more freedom for placement of your application files, if something were to cause your context settings to disappear, you will be able to quickly remedy the problem by running a context restore to get your applications running again right away. Instead of disabling SELinux, which you should never do, though many do, you should instead create custom policies that apply the proper SELinux context types to your directories and files. In these scenarios, SELinux will not allow Apache to access your content or log files. Your application may need to be installed in a separate directory or maybe, for other reasons, you want to place your content somewhere else.

SELinux can be very troublesome when deploying web applications on Red Hat while not using the default Apache directories, for either content or logs.