aboutsummaryrefslogtreecommitdiff
path: root/www/suphp/pkg-message
diff options
context:
space:
mode:
authorJeremy Chadwick <koitsu@FreeBSD.org>2007-12-11 20:38:58 +0000
committerJeremy Chadwick <koitsu@FreeBSD.org>2007-12-11 20:38:58 +0000
commitc28f2b3cca2651203a00c50c179535838f975943 (patch)
tree02df50241e1a1b983aa93dee72ce9275150ecc72 /www/suphp/pkg-message
parent9197058d9691a8fc970a59a6758dd5b53bae395b (diff)
downloadports-c28f2b3cca2651203a00c50c179535838f975943.tar.gz
ports-c28f2b3cca2651203a00c50c179535838f975943.zip
Notes
Diffstat (limited to 'www/suphp/pkg-message')
-rw-r--r--www/suphp/pkg-message43
1 files changed, 39 insertions, 4 deletions
diff --git a/www/suphp/pkg-message b/www/suphp/pkg-message
index e7187ad3eb00..45f278a74ba7 100644
--- a/www/suphp/pkg-message
+++ b/www/suphp/pkg-message
@@ -1,12 +1,47 @@
----------------------------------------------------------------
-You have installed mod_suphp, a module that provides a wrapper
-for PHP for Apache.
-
For help on using this module, please see the suPHP homepage:
http://www.suphp.org/
-Important hints:
Using suPHP can break some PHP-scripts, because of Apache's CGI
interface.
-----------------------------------------------------------------
+
+-----------------------------------------------------------------
+For those migrating from suPHP 0.5.x, be aware there are many
+changes in 0.6.x that can cause your current Apache environment
+to stop working or behave oddly. Here are two migration tips:
+
+suPHP now uses a configuration file for runtime configuration.
+The file is located at:
+
+ /usr/local/etc/suphp.conf
+
+...but *has not* been created for you. A sample configuration
+file has been installed here:
+
+ /usr/local/etc/suphp.conf-example
+
+This means that many of the make.conf(5) knobs for the
+www/suphp port are no longer used, and are modifiable in
+real-time; thus, things like WITHOUT_CHECKPATH and SUPHP_PATH
+are no longer needed. Instead, edit the config file.
+
+Equally as important, suPHP no longer uses a static MIME type
+for determining what content get handled by suPHP. In 0.5.x,
+you used the following Apache directives:
+
+ suPHP_Engine on
+ AddType application/x-httpd-php .php
+ AddHandler x-httpd-php .php
+
+In suPHP 0.6.x, you should use the following:
+
+ suPHP_Engine on
+ AddType x-httpd-php .php
+ suPHP_AddHandler x-httpd-php
+
+Otherwise, Apache will begin serving PHP files as downloadable
+content, rather than parse them with the PHP interpreter.
+-----------------------------------------------------------------
+