The document provides an overview of how to configure and run the Apache HTTP Server on FreeBSD. It discusses installing Apache from ports, editing the main configuration file httpd.conf to configure server settings like the server name, admin email, and document root. It also explains how to start, stop, and restart the server, set up virtual hosts, install additional modules, and use Apache to run dynamic websites built with frameworks like Django, Ruby on Rails, and applications like PHP.

1. APACHE HTTP SERVER INTRODUCION CONFIGURATION RUNNING APACHE VIRTUAL HOSTING APACHE MODULES DYNAMIC WEBSITE

2. INTRODUCTION 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

3. CONFIGURATION 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.

4. 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. Alows you to bind apache to specifid ip sddress and/or ports instead of the default The chamge of listen from specific ip address is Listen 12.34.56.78:80 Listen 80

5. SERVERADMIN The address to which problems with the server should be emailed. This address appears on some server-generated pages, such as error documents.

6. SERVERADMIN YOU @ YOUR . ADDRESS The address to which problems with the server should be emailed. This address appears on some server-generated pages, such as error documents. Server name gives the name and port that the aerver uses to identify itself this dan often etermined automatidally

7. DOCUMENTROOT "/USR/LOCAL/WWW/DATA" 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.

8. 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

9. 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

10. 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>

11. 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=&quot; &quot; Now that the web server is running, you can view your web site by pointing a web browser to http://localhost/. The default web page that is displayed is /usr/local/www/data/index.html.

12. VIRTUAL HOSTING 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 *

13. APACHE MODULES 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. Example : Load module foo_module modules / mod_foo.so

14. DYNAMIC WEBSITES 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.

15. MOD_SSL: 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.

16. LANGUAGE BINDINGS There are Apache modules for most major scripting languages. 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.

17. DJANGO 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.

18. Apache Configuration for Django/mod_python <Location &quot;/&quot;> SetHandler python-program PythonPath &quot;['/dir/to/your/django/packages/'] + sys.path&quot; PythonHandler django.core.handlers.modpython SetEnv DJANGO_SETTINGS_MODULE mysite.settings PythonAutoReload On PythonDebug On </Location>

19. Ruby on Rails 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;

20. MOD_PERL 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_PHP 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

21. THANK YOU