Setup a Full SAIL Stack on MacOS 10.5

Added by Stephen Bannasch, last edited by Stephen Bannasch on Aug 27, 2008  (view change)

Instructions for creating a full local SAIL Stack for MacOS 10.5

After completing steps 1 through 9 you will have a Java web start servlet delivering at least one versioned jnlp and all of it's associated jar resources along with a local SAIL Data Service. These resources can then be used to support a TELS Portal or any of the Concord DIY instances.

I highly recommend completing step 10: Install OTrunk Examples. This is a good way to test the web start servlet and SDS and is a fantastic resource showing a large collection of different OTrunk examples.

First decide on a directory in which to install all of this. I use ~/dev in the examples below.

You will need to execute part of step 7 again after setting up a portal/authoring environment in order to add the specific versioned jnlp and associated jar resources needed by that portal for delivering it's activities or reports.

Initial Steps

  1. Install up-to-date Apple Developer Tools
  2. Add /usr/local/bin to your path
  3. Install Subversion 1.5.x
  4. Install Mysql
  5. Install Maven 2.0.6 (or newer)
  6. Install Tomcat
  7. Install Jnlp Servlet and build associated WAR file with jnlp and jars
  8. Install Sail Data Service
  9. Setup Apache with mod_rails to serve the SDS
  10. Install OTrunk Examples
  11. Examples of configuration files


Install Apple Developer Tools

Install an up-to-date Apple Developer Tools if you don't have it already installed.

A copy of the Apple Developer Tools available at the time your computer was manufactured is available on a second DVD that came with the copy of the original OS.

You can download an up-to-date Apple Developer Tools by registering for a free account Apple Developer Connection account here: http://connect.apple.com. The download is about 1GB.

Apple Developer Tools installs the gcc toolchain which is needed for compiling any new native C or C++, libraries.

Add /usr/local/bin to your path

Many development tools are installed in the directory /usr/local/bin and this path should be added to the beginningof your PATH environmental variable.

Create the directory /usr/local/bin if it doesn't already exist:

mkdir -p /usr/local/bin

the -p option to mkdir creates the complete dir path specified if it doesn't exist

If you use bash you can add this to your PATH environmental variable in either your /.bash_profile or /.bash_rc files with a statement like his:

export PATH=/usr/local/bin:$PATH
{cpde}

_this adds the path {{/usr/local/bin}} to the beginning of any existing {{$PATH}} variable_

h3. Install Subversion 1.5.x

Binary distributions of Subversion for MacOS are available here: http://subversion.tigris.org/getting.html#osx


h4. Installing git (optional)

Git is distributed SCM which is much faster than subversion. In addition when using git you have a complete history of the repository cloned to your local hard drive. This means you can use local tools like gitk to easily browse all the recent changes in a repository without making network connections back to the main subversion repository.

At this point only the otrunk-examples code is also available as a git repository.

This wiki page describes how to install git using macports: https://confluence.concord.org/display/CCTR/Installing+git+with+macports

h3. Install Mysql:

From a package from mysql:
* http://dev.mysql.com/downloads/mysql/5.0.html#macosx-dmg

Or from source:
* http://hivelogic.com/articles/2007/11/installing-mysql-on-mac-os-x

I recommend setting a root password for mysql. In this document I will assume it is: 'password'

h3. Install Maven 2.0.6 (or newer)

* http://maven.apache.org/download.html

Create an .m2 dir in your home dir:

{code:language=shell|controls=true}
mkdir ~/.m2

and add the file settings.xml

<?xml version="1.0"?>
<settings>
  <servers>
    <server>
      <id>myserver</id>
      <username>myusername</username>
      <password>mypassword</password>
    </server>
  </servers>
</settings>

Install Tomcat

mkdir -p ~/dev/tomcat
  cd ~/dev/tomcat
  wget <binary distribution of tomcat>
  tar xzf <tomcat archive>

I installed tomcat v6.0.6 here:

~/dev/tomcat/tomcat-6_0_16

Create a separate tomcat dir for content:

mkdir tomcat6-base

Copy (don't move) these folders from tomcat_6_0_16 to tomcat6-base

  • conf
  • logs
  • shared (if you have it)
  • temp
  • webapps
  • work

Add to shell startup (on my system this is ~/.bash_profile) and source it

export JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Home
export CATALINA_HOME=/Users/stephen/dev/tomcat/tomcat-6_0_16
export CATALINA_BASE=/Users/stephen/dev/tomcat/tomcat6-base

dev/tomcat/tomcat6-base/conf/tomcat-users.xml

<?xml version='1.0' encoding='utf-8'?>
<tomcat-users>
  <role rolename="tomcat"/>
  <role rolename="role1"/>
  <role rolename="manager"/>
  <user username="user" password="password" roles="manager"/>
  <user username="tomcat" password="tomcat" roles="tomcat"/>
  <user username="both" password="tomcat" roles="tomcat,role1"/>
  <user username="role1" password="tomcat" roles="role1"/>
</tomcat-users>

Install tomcat shell script. See:

cd ~/dev/tomcat
curl http://www.encorewiki.org/download/attachments/20137/mytomcat.sh > mytomcat.sh
chmod +x mytomcat.sh

./mytomcat.sh start

Now open http://localhost:8080 in your browser and you should see tomcat running. Click on the manager link and enter the username and password you entered above and make sure you canopen the manager page.

To restart tomcat after making changes

./mytomcat.sh restart

Install Jnlp Servlet and build associated WAR file with jnlp and jars

You can do the following:

or just run the script below:
The specific instructions include a bash shell script.

The example below is an adaptation which loads the snapshot tels and all-otrunk jnlps and jars and copies the results to $CATALINA_BASE/webapps/jnlp.

mkdir -p jnlp-servlet-work/jnlp-servlet; cd jnlp-servlet-work/jnlp-servlet                                 
curl http://confluence.concord.org/download/attachments/16444/empty-jnlp-servlet.war | jar x               
curl http://jnlp.concord.org/dev/org/concord/jnlp2shell/jnlp2shell-1.0-SNAPSHOT.jar > ../jnlp2shell.jar     
SERVLET_JNLPS="
  http://tels-develop.soe.berkeley.edu:8080/jnlp/org/telscenter/jnlp/plr-everything-jdic-otrunk-snapshot/plr-everything-jdic-otrunk-snapshot.jnlp
  http://jnlp.concord.org/dev/org/concord/maven-jnlp/all-otrunk-snapshot/all-otrunk-snapshot.jnlp"
for jnlp_url in $SERVLET_JNLPS  
do   
  java -cp ../jnlp2shell.jar org.concord.JnlpServletCacher $jnlp_url . 
done
mkdir $CATALINA_BASE/webapps/jnlp
cp -r * $CATALINA_BASE/webapps/jnlp

You can test whether your tomcat server is serving the jnlp with a curl command from the shell:

curl -I http://localhost:8080/jnlp/org/concord/maven-jnlp/all-otrunk-snapshot/all-otrunk-snapshot.jnlp

A successful response will look something like this:

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Last-Modified: Tue, 05 Aug 2008 21:28:43 GMT
Content-Type: application/x-java-jnlp-file
Content-Length: 10443
Date: Wed, 06 Aug 2008 04:29:08 GMT

You can edit the specific jnlps listed in the SERVLET_JNLPS variable to load specific versions of the jnlp and associated versioned jar resources.

Running the script above twice will load any newer jnlp and jar resources without deleting the older ones.

Any specific SAIL/OTrunk instance run by a Portal or Authoring system will either use a specific versioned jnlp (the resources referenced by this type of jnlp are frozen) or a snapshot jnlp which changes whenever a new build is released by a development group.

Both Concord and the Berekeley TELS groups generate jnlp and jar repositories. Here are the root directories for each repository. You can see all the jnlp families available by browsing these locations.

Generating versioned jnlps and jars programmatically

This page: Setup JNLP Deployment Environment on the Concord Consortium wiki describes how to use maven to generate version jnlps and jars programmatically for an entire family of jnlps.

Install Sail Data Service

Use subversion to checkout the SDS Ruby on Rails application:

cd ~/dev
svn co http://svn.concord.org/svn/sds/trunk sds
cd sds

Setup the SDS environment

cd config
cp environment.sample.rb environment.rb
cp database.sample.yml database.yml

Edit the file database.yml and specify the names of the mysql databases to use.

Unless you are doing active development I recommend using the same database for development and production.

Here is a sample:

development:
  adapter: <% if RUBY_PLATFORM =~ /java/ %>jdbcmysql<% else %>mysql<% end %>
  encoding: utf8
  host: localhost
  database: sds_2_1_local_development
  username: root
  password: password

test:
  adapter: <% if RUBY_PLATFORM =~ /java/ %>jdbcmysql<% else %>mysql<% end %>
  encoding: utf8
  host: localhost
  database: sds_2_1_local_test
  username: root
  password: password
  socket: /tmp/mysql.sock

production:
  adapter: <% if RUBY_PLATFORM =~ /java/ %>jdbcmysql<% else %>mysql<% end %>
  encoding: utf8
  host: localhost
  database: sds_2_1_local_development
  username: root
  password: password
  socket: /tmp/mysql.sock

Install a needed rubygem:

sudo gem install ruby-debug

Create the blank databases:

rake db:create:all

Create all the database tables:

rake db:migrate

Create the default jnlp session configuration templates:

rake sds_config:setup_all_config_versions

Do a simple smoke test of the SDS by starting it from the shell, in the script directory run the following script:

script/server

And open http://localhost:3000 in a browser. You should see the SDS home page.

Type Ctrl-C in the shell to stop this server.

Setup Apache with mod_rails to serve the SDS

First install the ruby gem for running rails applications in Apache using Phusion Passenger (aka mod_rails)

Detailed instructions: http://www.modrails.com/install.html

sudo gem install passenger
sudo passenger-install-apache2-module

Enable Apache virtual hosts and add one referencing the SDS.

(reference: http://httpd.apache.org/docs/2.2/vhosts/)

In the file: /private/etc/apache2/httpd.conf uncomment this line to enable Apache2 the include of the separate file defining Apache virtual hosts:

Include /private/etc/apache2/extra/httpd-vhosts.conf

In the file: /private/etc/apache2/extra/httpd-vhosts.conf first add this line (reference: namevirtualhost):

NameVirtualHost 127.0.0.1

Then delete or comment the sample vhosts and add this one:

Replace the path /Users/stephen with the actual path to your home directory.

<VirtualHost 127.0.0.1>
  DocumentRoot "/Users/stephen/dev/sds/public"
  ServerName saildataservice
  ErrorLog "/Users/stephen/dev/sds/log/error.log"
  <Directory "/Users/stephen/dev/sds/public">
     Options FollowSymLinks MultiViews Includes
     AllowOverride All
     Order allow,deny
     Allow from all
  </Directory>
</VirtualHost>

Make sure your Apache configuration files are valid:

apachectl configtest

Fix any errors before going on.

Add a local hostname in /etc/hosts

In the file: /etc/hosts

Add this line to create a host named saildataservice that references localhost:

127.0.0.1       saildataservice

Restart apache:

sudo apachectl restart

Now load this page in your browser:

Install OTrunk Examples

Setup a local copy of OTrunk Examples

Add the all-otrunk snapshot jnlp to your jnlp servelet (see step 6)

Checkout a copy of otrunk-examples

In your dev directory checkout using subversion the otrunk examples:

svn co http://svn.concord.org/svn/projects/trunk/common/java/otrunk/otrunk-examples

Later if you want to update the otrunk-examples folder do this:

cd ~/dev/otrunk-examples
svn up

If you have git installed you can clone the otrunk examples instead. The initial download and updates will be much quicker than subversion. Using git and also allows you to make local branches of the examples and even push your branches to another public repository like github without having commit access to the main svn repository.

git clone git://github.com/stepheneb/otrunk-examples.git

Later if you want to update the otrunk-examples folder do this:

cd ~/dev/otrunk-examples
git pull

Create an SDS Portal realm and associated resources for otrunk-examples

Create a new SDS portal realm, jnlp, curnit, sail_user, offerng and workgroup for OTrunk testing

Execute the ruby script setup_otrunk_testing_portal.rb using the Rails script/runnner command to create a Portal realm environment for running the OTrunk Examples.

Change to the sds directory:

cd ~/dev/sds

Save this script in the sds directory as setup_otrunk_testing_portal.rb

setup_otrunk_testing_portal.rb
p = Portal.create(:name => "OTrunk Examples", :use_authentication => false, :title => "OTrunk Examples", 
:vendor => "Concord Consortium", :home_page_url => "https://confluence.concord.org/display/CSP/OTrunk", 
:description => "A test.", :image_url => "/images/sail_orangecirc_64.gif", :last_bundle_only =>  true)
c = Curnit.create(:portal_id => p.id, :name => "diy curnit stub", 
:always_update => false, :url => "http://saildataservice/curnits/otrunk-curnit-external-diytest.jar")
j = Jnlp.create(:portal_id => p.id, :name => "all otrunk Snapshot", :always_update => true, 
:url => "http://localhost:8080/jnlp/org/concord/maven-jnlp/all-otrunk-snapshot/all-otrunk-snapshot.jnlp")
u = SailUser.create(:portal_id => p.id, :first_name => "OTrunk", :last_name => "Examples")
o = Offering.create(:portal_id => p.id, :name => "OTrunk Examples", :curnit_id => c.id, :jnlp_id => j.id)
w = Workgroup.create(:portal_id => p.id, :name => "OTrunk Examples", :offering_id => o.id)
wm = w.workgroup_memberships.create(:sail_user_id => u.id, :version => w.version)
rs = ActionController::Routing::Routes
view = rs.generate(:pid => p.id, :controller => "offering", :action => "jnlp", :id => o.id, 
:wid => w.id, :type => "workgroup", :savedata => nil, :only_path => false)
puts "*** view path ***"
puts "http://saildataservice" + view

Execute the script in the rails context:

script/runner setup_otrunk_testing_portal.rb

Create the file local_sds_path

Enter the 'view' path to the OTrunk Testing workgroup in the OTrunk Testing offering to the file local_sds_path in the dir otrunk-examples/index-builder-script.

Replace the value below with the one printed at the end of running the script segment just above.

cd ~/dev/otrunk-examples/index-builder-script/
echo 'http://saildataservice/4/offering/2/jnlp/2/view' > local_sds_path

Generate the local ot-index.html files

In the otrunk-examples directory run the /build-index-local.rb script.

cd ~/dev/otrunk-examples
ruby index-builder-script/build-index-local.rb

Create a new Apache vhost for otrunk-examples

Add this new Apache virtual host in the file: /private/etc/apache2/extra/httpd-vhosts.conf:

Replace the path /Users/stephen with the actual path to your home directory.

<VirtualHost *:80>
  DocumentRoot "/Users/stephen/dev/otrunk-examples"
  ServerName otrunk-examples
  <Directory "/Users/stephen/dev/otrunk-examples">
     Options FollowSymLinks MultiViews Includes
     AllowOverride All
     Order allow,deny
     Allow from all
  </Directory>
</VirtualHost>

In the file: /etc/hosts add this line to create a host named otrunk-examples that references localhost:

127.0.0.1       otrunk-examples

Restart apache:

sudo apachectl restart

Now open this page in your browser: http://otrunk-examples/example-index.html to see all of Concord's OTrunk Examples.

Example of configuration files

Here are examples of the Apache and hosts configuration files on my computer:

/etc/hosts

/etc/hosts
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1	localhost
255.255.255.255	broadcasthost
::1             localhost 
fe80::1%lo0	localhost
127.0.0.1       otrunk-examples
127.0.0.1       saildataservice

/private/etc/apache2/extra/httpd-vhosts.conf

/private/etc/apache2/extra/httpd-vhosts.conf
NameVirtualHost 127.0.0.1

<VirtualHost 127.0.0.1>
	DocumentRoot "/Users/stephen/dev/concord/java/otrunk-examples"
	ServerName otrunk-examples
	ErrorLog "/Users/stephen/dev/rails/otrunk-examples/log/error.log"
	AddOutputFilterByType DEFLATE text/html text/plain text/xml
	<Directory "/Users/stephen/dev/concord/java/otrunk-examples">
	     Options FollowSymLinks MultiViews Includes
	     AllowOverride All
	     Order allow,deny
	     Allow from all
	</Directory>
</VirtualHost>

<VirtualHost 127.0.0.1>
	DocumentRoot "/Users/stephen/dev/rails/sds_local/public"
	ServerName saildataservice
	ErrorLog "/Users/stephen/dev/rails/sds_local/log/error.log"
	<Directory "/Users/stephen/dev/rails/sds_local/public">
	     Options FollowSymLinks MultiViews Includes
	     AllowOverride All
	     Order allow,deny
	     Allow from all
	</Directory>
</VirtualHost>

/private/etc/apache2/httpd.conf

/private/etc/apache2/httpd.conf
#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see 
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "/private/var/log/apache2/foo.log"
# with ServerRoot set to "/usr" will be interpreted by the
# server as "/usr//private/var/log/apache2/foo.log".

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk.  If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "/usr"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to 
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule authn_file_module libexec/apache2/mod_authn_file.so
LoadModule authn_dbm_module libexec/apache2/mod_authn_dbm.so
LoadModule authn_anon_module libexec/apache2/mod_authn_anon.so
LoadModule authn_dbd_module libexec/apache2/mod_authn_dbd.so
LoadModule authn_default_module libexec/apache2/mod_authn_default.so
LoadModule authz_host_module libexec/apache2/mod_authz_host.so
LoadModule authz_groupfile_module libexec/apache2/mod_authz_groupfile.so
LoadModule authz_user_module libexec/apache2/mod_authz_user.so
LoadModule authz_dbm_module libexec/apache2/mod_authz_dbm.so
LoadModule authz_owner_module libexec/apache2/mod_authz_owner.so
LoadModule authz_default_module libexec/apache2/mod_authz_default.so
LoadModule auth_basic_module libexec/apache2/mod_auth_basic.so
LoadModule auth_digest_module libexec/apache2/mod_auth_digest.so
LoadModule cache_module libexec/apache2/mod_cache.so
LoadModule disk_cache_module libexec/apache2/mod_disk_cache.so
LoadModule mem_cache_module libexec/apache2/mod_mem_cache.so
LoadModule dbd_module libexec/apache2/mod_dbd.so
LoadModule dumpio_module libexec/apache2/mod_dumpio.so
LoadModule ext_filter_module libexec/apache2/mod_ext_filter.so
LoadModule include_module libexec/apache2/mod_include.so
LoadModule filter_module libexec/apache2/mod_filter.so
LoadModule deflate_module libexec/apache2/mod_deflate.so
LoadModule log_config_module libexec/apache2/mod_log_config.so
LoadModule log_forensic_module libexec/apache2/mod_log_forensic.so
LoadModule logio_module libexec/apache2/mod_logio.so
LoadModule env_module libexec/apache2/mod_env.so
LoadModule mime_magic_module libexec/apache2/mod_mime_magic.so
LoadModule cern_meta_module libexec/apache2/mod_cern_meta.so
LoadModule expires_module libexec/apache2/mod_expires.so
LoadModule headers_module libexec/apache2/mod_headers.so
LoadModule ident_module libexec/apache2/mod_ident.so
LoadModule usertrack_module libexec/apache2/mod_usertrack.so
#LoadModule unique_id_module libexec/apache2/mod_unique_id.so
LoadModule setenvif_module libexec/apache2/mod_setenvif.so
LoadModule version_module libexec/apache2/mod_version.so
LoadModule proxy_module libexec/apache2/mod_proxy.so
LoadModule proxy_connect_module libexec/apache2/mod_proxy_connect.so
LoadModule proxy_ftp_module libexec/apache2/mod_proxy_ftp.so
LoadModule proxy_http_module libexec/apache2/mod_proxy_http.so
LoadModule proxy_ajp_module libexec/apache2/mod_proxy_ajp.so
LoadModule proxy_balancer_module libexec/apache2/mod_proxy_balancer.so
LoadModule ssl_module libexec/apache2/mod_ssl.so
LoadModule mime_module libexec/apache2/mod_mime.so
LoadModule dav_module libexec/apache2/mod_dav.so
LoadModule status_module libexec/apache2/mod_status.so
LoadModule autoindex_module libexec/apache2/mod_autoindex.so
LoadModule asis_module libexec/apache2/mod_asis.so
LoadModule info_module libexec/apache2/mod_info.so
LoadModule cgi_module libexec/apache2/mod_cgi.so
LoadModule dav_fs_module libexec/apache2/mod_dav_fs.so
LoadModule vhost_alias_module libexec/apache2/mod_vhost_alias.so
LoadModule negotiation_module libexec/apache2/mod_negotiation.so
LoadModule dir_module libexec/apache2/mod_dir.so
LoadModule imagemap_module libexec/apache2/mod_imagemap.so
LoadModule actions_module libexec/apache2/mod_actions.so
LoadModule speling_module libexec/apache2/mod_speling.so
LoadModule userdir_module libexec/apache2/mod_userdir.so
LoadModule alias_module libexec/apache2/mod_alias.so
LoadModule rewrite_module libexec/apache2/mod_rewrite.so
LoadModule bonjour_module     libexec/apache2/mod_bonjour.so
#LoadModule php5_module        libexec/apache2/libphp5.so
#LoadModule fastcgi_module     libexec/apache2/mod_fastcgi.so

# Phusion Passenger "mod_rails"
LoadModule passenger_module /Library/Ruby/Gems/1.8/gems/passenger-2.0.2/ext/apache2/mod_passenger.so
PassengerRoot /Library/Ruby/Gems/1.8/gems/passenger-2.0.2
PassengerRuby /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby

RailsSpawnMethod conservative

<IfModule !mpm_netware_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.  
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User www
Group staff
</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin you@example.com

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName www.example.com:80

#
# 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.
#
DocumentRoot "/Library/WebServer/Documents"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories). 
#
# First, we configure the "default" to be a very restrictive set of 
# features.  
#
<Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "/Library/WebServer/Documents">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks MultiViews

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Order allow,deny
    Allow from all

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.html
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being 
# viewed by Web clients. 
#
<FilesMatch "^\.([Hh][Tt]|[Dd][Ss]_[Ss])">
    Order allow,deny
    Deny from all
    Satisfy All
</FilesMatch>

#
# Apple specific filesystem protection.
#
<Files "rsrc">
    Order allow,deny
    Deny from all
    Satisfy All
</Files>
<DirectoryMatch ".*\.\.namedfork">
    Order allow,deny
    Deny from all
    Satisfy All
</DirectoryMatch>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog /private/var/log/apache2/error_log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog /private/var/log/apache2/access_log common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog /private/var/log/apache2/access_log combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to 
    # exist in your server's namespace, but do not anymore. The client 
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts. 
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAliasMatch ^/cgi-bin/((?!(?i:webobjects)).*$) "/Library/WebServer/CGI-Executables/$1"

</IfModule>

<IfModule cgid_module>
    #
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #
    #Scriptsock /private/var/run/cgisock
</IfModule>

#
# "/Library/WebServer/CGI-Executables" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/Library/WebServer/CGI-Executables">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>

#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig /private/etc/apache2/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile /private/etc/apache2/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# EnableMMAP and EnableSendfile: On systems that support it, 
# memory-mapping or the sendfile syscall is used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted 
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the /private/etc/apache2/extra/ directory can be 
# included to add extra features or to modify the default configuration of 
# the server, or you may simply copy their contents here and change as 
# necessary.

# Server-pool management (MPM specific)
Include /private/etc/apache2/extra/httpd-mpm.conf

# Multi-language error messages
#Include /private/etc/apache2/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
Include /private/etc/apache2/extra/httpd-autoindex.conf

# Language settings
Include /private/etc/apache2/extra/httpd-languages.conf

# User home directories
Include /private/etc/apache2/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include /private/etc/apache2/extra/httpd-info.conf

# Virtual hosts
Include /private/etc/apache2/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
Include /private/etc/apache2/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include /private/etc/apache2/extra/httpd-dav.conf

# Various default settings
#Include /private/etc/apache2/extra/httpd-default.conf

# Secure (SSL/TLS) connections
#Include /private/etc/apache2/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

Include /private/etc/apache2/other/*.conf
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.