# TypesConfig points to the file containing the list of mappings from # filename extension to MIME-type. #
TypesConfig conf/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 AddType application/x-httpd-php .php
#
# AddHandler allows you to map certain file extensions to \ # 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 \ #
#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 \
#
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml #
# 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 conf/magic #
# Customizable error responses come in three flavors: # 1) plain text 2) local redirects 3) external redirects #
# Some examples:
#ErrorDocument 500 \#ErrorDocument 404 /missing.html
#ErrorDocument 404 \
#ErrorDocument 402 http://www.example.com/subscription_info.html # #
# MaxRanges: Maximum number of Ranges in a request before # returning the entire resource, or one of the special # values 'default', 'none' or 'unlimited'. # Default setting is to accept 200 Ranges. #MaxRanges unlimited #
# EnableMMAP and EnableSendfile: On systems that support it, # memory-mapping or the sendfile syscall may be 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.
# Defaults: EnableMMAP On, EnableSendfile Off #
#EnableMMAP off #EnableSendfile on
# Supplemental configuration #
# The configuration files in the conf/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 conf/extra/httpd-mpm.conf
# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf
# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf
# Language settings
#Include conf/extra/httpd-languages.conf
# User home directories
#Include conf/extra/httpd-userdir.conf
# Real-time info on requests and configuration #Include conf/extra/httpd-info.conf
# Virtual hosts
Include conf/extra/httpd-vhosts.conf
# Local access to the Apache HTTP Server Manual #Include conf/extra/httpd-manual.conf
# Distributed authoring and versioning (WebDAV) #Include conf/extra/httpd-dav.conf
# Various default settings
#Include conf/extra/httpd-default.conf Include conf/extra/httpd-proxy.conf
# Configure mod_proxy_html to understand HTML4/XHTML1
# Secure (SSL/TLS) connections #Include conf/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. #
SSLRandomSeed startup builtin SSLRandomSeed connect builtin httpd-proxy.conf
ProxyPass ajp://localhost:8009/
httpd-vhosts.conf # Virtual Hosts #
# Required modules: mod_log_config
# If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations # use only name-based virtual hosts so the server doesn't need to worry about # IP addresses. This is indicated by the asterisks in the directives below. #
# Please see the documentation at
#
# for further details before you try to setup virtual hosts. #
# You may use the command line option '-S' to verify your virtual host # configuration. #
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container. # The first VirtualHost section is used for all requests that do not # match a ServerName or ServerAlias in any
ServerAdmin webmaster@wifidog.com
DocumentRoot \ ServerName wifidog.com ServerAlias wifidog
Alias /sf /var/www/authpuppy/lib/vendor/symfony/data/web/sf/ Alias /php-cgi /usr/local/php/bin/php-cgi ErrorLog \
CustomLog \ LogLevel debug php.ini [PHP]
;;;;;;;;;;;;;;;;;;;
; About php.ini ; ;;;;;;;;;;;;;;;;;;;
; PHP's initialization file, generally called php.ini, is responsible for ; configuring many of the aspects of PHP's behavior.
; PHP attempts to find and load this configuration from a number of locations. ; The following is a summary of its search order: ; 1. SAPI module specific location.
; 2. The PHPRC environment variable. (As of PHP 5.2.0)
; 3. A number of predefined registry keys on Windows (As of PHP 5.2.0) ; 4. Current working directory (except CLI)
; 5. The web server's directory (for SAPI modules), or directory of PHP ; (otherwise in Windows)
; 6. The directory from the --with-config-file-path compile time option, or the ; Windows directory (C:\\windows or C:\\winnt) ; See the PHP docs for more specific information. ; http://php.net/configuration.file
; The syntax of the file is extremely simple. Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably guessed). ; Section headers (e.g. [Foo]) are also silently ignored, even though ; they might mean something in the future.
; Directives following the section heading [PATH=/www/mysite] only ; apply to PHP files in the /www/mysite directory. Directives
; following the section heading [HOST=www.example.com] only apply to ; PHP files served from www.example.com. Directives set in these ; special sections cannot be overridden by user-defined INI files or ; at runtime. Currently, [PATH=] and [HOST=] sections only work under ; CGI/FastCGI.
; http://php.net/ini.sections
; Directives are specified using the following syntax: