FreeBSD is used to run some of the busiest web sites in the world. The majority of web
servers on the Internet are using the Apache HTTP Server. Apache software packages should be included on your FreeBSD
installation media. If you did not install Apache when you
first installed FreeBSD, then you can install it from the www/apache13 or www/apache22 port.
Once Apache has been installed successfully, it must be
configured.
Note: This section covers version 1.3.X of the Apache
HTTP Server as that is the most widely used version for FreeBSD. Apache 2.X introduces many new technologies but they are not
discussed here. For more information about Apache 2.X,
please see https://httpd.apache.org/.
The main Apache HTTP Server configuration file is installed
as /usr/local/etc/apache/httpd.conf on FreeBSD. This file is a
typical UNIX® text configuration file with comment
lines beginning with the # character. A comprehensive
description of all possible configuration options is outside the scope of this book, so
only the most frequently modified directives will be described here.
- ServerRoot "/usr/local"
-
This specifies the default directory hierarchy for the Apache installation. Binaries are stored in the bin and sbin subdirectories of the server
root, and configuration files are stored in etc/apache.
- ServerAdmin [email protected]
-
The address to which problems with the server should be emailed. This address appears
on some server-generated pages, such as error documents.
- ServerName www.example.com
-
ServerName allows you to set a host name which is sent back
to clients for your server if it is different to the one that the host is configured with
(i.e., use www instead of the host's real name).
- DocumentRoot "/usr/local/www/data"
-
DocumentRoot: The directory out of which you will serve your
documents. By default, all requests are taken from this directory, but symbolic links and
aliases may be used to point to other locations.
It is always a good idea to make backup copies of your Apache configuration file before making changes. Once you are
satisfied with your initial configuration you are ready to start running Apache.
Apache does not run from the inetd super server as many other network servers do. It is
configured to run standalone for better performance for incoming HTTP requests from
client web browsers. A shell script wrapper is included to make starting, stopping, and
restarting the server as simple as possible. To start up Apache for the first time, just run:
# /usr/local/sbin/apachectl start
You can stop the server at any time by typing:
# /usr/local/sbin/apachectl stop
After making changes to the configuration file for any reason, you will need to
restart the server:
# /usr/local/sbin/apachectl restart
To restart Apache without aborting current connections,
run:
# /usr/local/sbin/apachectl graceful
Additional information available at
apachectl(8)
manual page.
To launch Apache at system startup, add the following line
to /etc/rc.conf:
apache_enable="YES"
or for Apache 2.2:
apache22_enable="YES"
If you would like to supply additional command line options for the Apache httpd program started at system
boot, you may specify them with an additional line in rc.conf:
apache_flags=""
Now that the web server is running, you can view your web site by pointing a web
browser to https://localhost/. The default web page that is
displayed is /usr/local/www/data/index.html.
Apache supports two different types of Virtual Hosting. The
first method is Name-based Virtual Hosting. Name-based virtual hosting uses the clients
HTTP/1.1 headers to figure out the hostname. This allows many different domains to share
the same IP address.
To setup Apache to use Name-based Virtual Hosting add an
entry like the following to your httpd.conf:
NameVirtualHost *
If your webserver was named www.domain.tld and you wanted to
setup a virtual domain for www.someotherdomain.tld then you would
add the following entries to httpd.conf:
<VirtualHost *>
ServerName www.domain.tld
DocumentRoot /www/domain.tld
</VirtualHost>
<VirtualHost *>
ServerName www.someotherdomain.tld
DocumentRoot /www/someotherdomain.tld
</VirtualHost>
Replace the addresses with the addresses you want to use and the path to the documents
with what you are using.
For more information about setting up virtual hosts, please consult the official Apache documentation at: https://httpd.apache.org/docs/vhosts/.
There are many different Apache modules available to add
functionality to the basic server. The FreeBSD Ports Collection provides an easy way to
install Apache together with some of the more popular add-on
modules.
The mod_ssl module uses the OpenSSL library to provide
strong cryptography via the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security
(TLS v1) protocols. This module provides everything necessary to request a signed
certificate from a trusted certificate signing authority so that you can run a secure web
server on FreeBSD.
If you have not yet installed Apache, then a version of Apache 1.3.X that includes mod_ssl may
be installed with the www/apache13-modssl port. SSL support is also available for Apache 2.X in the www/apache22 port, where it is enabled by default.
There are Apache modules for most major scripting languages. These modules typically
make it possible to write Apache modules entirely in a
scripting language. They are also often used as a persistent interpreter embedded into
the server that avoids the overhead of starting an external interpreter and the
startup-time penalty for dynamic websites, as described in the next section.
In the last decade, more businesses have turned to the Internet in order to enhance
their revenue and increase exposure. This has also increased the need for interactive web
content. While some companies, such as Microsoft®,
have introduced solutions into their proprietary products, the open source community
answered the call. Modern options for dynamic web content include Django, Ruby on Rails,
mod_perl, and mod_php.
Django is a BSD licensed framework designed to allow developers to write high
performance, elegant web applications quickly. It provides an object-relational mapper so
that data types are developed as Python objects, and a rich dynamic database-access API
is provided for those objects without the developer ever having to write SQL. It also
provides an extensible template system so that the logic of the application is separated
from the HTML presentation.
Django depends on mod_python, Apache, and an SQL database engine of your choice. The FreeBSD
Port will install all of these pre-requisites for you with the appropriate flags.
Example 27-3. Installing Django with Apache2, mod_python3, and PostgreSQL
# cd /usr/ports/www/py-django; make all install clean -DWITH_MOD_PYTHON3 -DWITH_POSTGRESQL
Once Django and these pre-requisites are installed, you will need to create a Django
project directory and then configure Apache to use the embedded Python interpreter to
call your application for specific URLs on your site.
Example 27-4. Apache Configuration for Django/mod_python
You will need to add a line to the apache httpd.conf file to
configure Apache to pass requests for certain URLs to your web application:
<Location "/">
SetHandler python-program
PythonPath "['/dir/to/your/django/packages/'] + sys.path"
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE mysite.settings
PythonAutoReload On
PythonDebug On
</Location>
Ruby on Rails is another open source web framework that provides a full development
stack and is optimized to make web developers more productive and capable of writing
powerful applications quickly. It can be installed easily from the ports system.
# cd /usr/ports/www/rubygem-rails; make all install clean
The Apache/Perl integration project brings together the
full power of the Perl programming language and the Apache HTTP
Server. With the mod_perl module it is possible to write
Apache modules entirely in Perl. In addition, the persistent
interpreter embedded in the server avoids the overhead of starting an external
interpreter and the penalty of Perl start-up time.
mod_perl is available a few different ways. To use mod_perl remember that mod_perl 1.0
only works with Apache 1.3 and mod_perl 2.0 only works with Apache
2.X. mod_perl 1.0 is available in www/mod_perl and a statically compiled version is available in
www/apache13-modperl. mod_perl 2.0
is avaliable in www/mod_perl2.
Written by Tom Rhodes.
PHP, also known as “PHP: Hypertext
Preprocessor” is a general-purpose scripting language that is especially suited for
Web development. Capable of being embedded into HTML
its syntax draws upon C, Java™, and Perl with the
intention of allowing web developers to write dynamically generated webpages quickly.
To gain support for PHP5 for the Apache web server, begin by installing the lang/php5 port.
If the lang/php5 port is being installed for the first time, available
OPTIONS will be displayed automatically. If a menu is not
displayed, i.e. because the lang/php5 port has been installed some time in the past, it is
always possible to bring the options dialog up again by running:
# make config
in the port directory.
In the options dialog, check the APACHE option to build mod_php5 as a loadable module for the Apache web server.
Note: A lot of sites are still using PHP4
for various reasons (i.e. compatibility issues or already deployed web applications). If
the mod_php4 is needed instead of mod_php5, then please use the lang/php4 port. The lang/php4 port supports many of the configuration and
build-time options of the lang/php5 port.
This will install and configure the modules required to support dynamic PHP applications. Check to ensure the following sections have
been added to /usr/local/etc/apache/httpd.conf:
LoadModule php5_module libexec/apache/libphp5.so
AddModule mod_php5.c
<IfModule mod_php5.c>
DirectoryIndex index.php index.html
</IfModule>
<IfModule mod_php5.c>
AddType application/x-httpd-php .php
AddType application/x-httpd-php-source .phps
</IfModule>
Once completed, a simple call to the apachectl command for a
graceful restart is needed to load the PHP module:
# apachectl graceful
For future upgrades of PHP, the make config command will not be required; the selected OPTIONS are saved automatically by the FreeBSD Ports framework.
The PHP support in FreeBSD is extremely modular so
the base install is very limited. It is very easy to add support using the lang/php5-extensions port. This port provides a menu driven
interface to PHP extension installation.
Alternatively, individual extensions can be installed using the appropriate port.
For instance, to add support for the MySQL database server
to PHP5, simply install the databases/php5-mysql port.
After installing an extension, the Apache server must be
reloaded to pick up the new configuration changes:
# apachectl graceful
