Re: Help getting wordpress working oon 4.11

2006-01-22 Thread stan
On Sun, Jan 22, 2006 at 07:19:18PM +0100, David Raison wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi Stan,
> 
> add the following to your httpd.conf
> 
> AddType application/x-httpd-php .php
> AddType application/x-httpd-php-source  .phps
> 
> And index.php to the DirectoryIndex (so your index.php file gets
> loaded automatically if no filename is supplied)
> 
> 
> DirectoryIndex index.php index.html
> 
> 
> but I'm not sure if this is the same with apache 1.3 (I'm using 2.2)
> you may also need to add the following:
> 
> LoadModule php5_modulelibexec/apache22/libphp5.so #
> php4_module if you're using php4
> 
A quick check of my httpd.conf looks like all of these have been done. I'm
using Apache 1.3 BTW.

Here's the file, in case anyone can see the error of my ways.

Thanks for any help.


##
## httpd.conf -- Apache HTTP server configuration file
##

#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/> for detailed information about
# the directives.
#
# 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.  
#
# After this file is processed, the server will look for and process
# /usr/local/etc/apache/srm.conf and then /usr/local/etc/apache/access.conf
# unless you have overridden these with ResourceConfig and/or
# AccessConfig directives here.
#
# The configuration directives are grouped into three basic sections:
#  1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
#  2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
#  3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
#
# 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 "logs/foo.log"
# with ServerRoot set to "/usr/local/apache" will be interpreted by the
# server as "/usr/local/apache/logs/foo.log".
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# ServerType is either inetd, or standalone.  Inetd mode is only supported on
# Unix platforms.
#
ServerType standalone

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation
# (available at http://www.apache.org/docs/mod/core.html#lockfile>);
# you will save yourself a lot of trouble.
#
ServerRoot "/usr/local"

#
# The LockFile directive sets the path to the lockfile used when Apache
# is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or
# USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be left at
# its default value. The main reason for changing it is if the logs
# directory is NFS mounted, since the lockfile MUST BE STORED ON A LOCAL
# DISK. The PID of the main server process is automatically appended to
# the filename. 
#
#LockFile /var/run/httpd.lock

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
#
PidFile /var/run/httpd.pid

#
# ScoreBoardFile: File used to store internal server process information.
# Not all architectures require this.  But if yours does (you'll know because
# this file will be  created when you run Apache) then you *must* ensure that
# no two invocations of Apache share the same scoreboard file.
#
ScoreBoardFile /var/run/httpd.scoreboard

#
# In the standard configuration, the server will process httpd.conf (this 
# file, specified by the -f command line option), srm.conf, and access.conf 
# in that order.  The latter two files are now distributed empty, as it is 
# recommended that all directives be kept in a single file for simplicity.  
# The commented-out values below are the built-in defaults.  You can have the 
# server ignore these files altogether by using "/dev/null" (for Unix) or
# "nul" (for Win32) for the arguments to the directives.
#
#ResourceConfig /usr/local/etc/apache/srm.conf
#AccessConfig /usr/local/etc/apache/access.conf

#
# Timeout: The number of seconds befor

Re: Help getting wordpress working oon 4.11

2006-01-22 Thread David Raison
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Stan,

add the following to your httpd.conf

AddType application/x-httpd-php .php
AddType application/x-httpd-php-source  .phps

And index.php to the DirectoryIndex (so your index.php file gets
loaded automatically if no filename is supplied)


DirectoryIndex index.php index.html


but I'm not sure if this is the same with apache 1.3 (I'm using 2.2)
you may also need to add the following:

LoadModule php5_modulelibexec/apache22/libphp5.so #
php4_module if you're using php4

stan wrote:

> I'm trying to set up wordpress on a fairly current 4.11 machine.
>
> I've installed the wordpress port, and the mysql 1.41 port. I've
> created a mysql database called wordpress, and I can access it from
> the command line with mysql.
>
> I'm able to access the setup instructions from apache on that
> machine. They say to run the ~/admin/install.php script. The
> problem is that when I do that, instead of executing it, it is just
> displayed.
>
> I suspect that I need to change the apache config to _execute_ php
> code, but I can't figure out how.
>
> Any digestions?
>
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD08ym/sLffsMilEkRAv9tAJ9wsLppp6Y8/A7YzSNkwscv7rRtUACghMBe
m0GUE0yORXnU01z9qXxCqcc=
=I1Y2
-END PGP SIGNATURE-

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Help getting wordpress working oon 4.11

2006-01-22 Thread stan
I'm trying to set up wordpress on a fairly current 4.11 machine.

I've installed the wordpress port, and the mysql 1.41 port. I've created a
mysql database called wordpress, and I can access it from the command line
with mysql.

I'm able to access the setup instructions from apache on that machine. They
say to run the ~/admin/install.php script. The problem is that when I do
that, instead of executing it, it is just displayed.

I suspect that I need to change the apache config to _execute_ php code,
but I can't figure out how.

Any digestions?

-- 
U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong 
Terror 
- New York Times 9/3/1967
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"