On Fri, 25 Jun 2004 10:26:05 -0700 Arthaey Angosii <arthaey@...> wrote:
> I recently downloaded phpwiki-1.3.10 onto my Mandrake 9.2 computer,
> running MySQL 4.0.15, PHP (looks like version 4.3.2, maybe... how do I
Probably 4.3.2 based on what Apache's telling you. Two other ways of getting the version number are via your package management system (rpm -qa | egrep -i php) and asking Apache directly:
$ telnet http://www.example.com 80
Connected to http://www.example.com.
Escape character is '^]'.
HEAD /index.html HTTP/1.0
HTTP/1.1 302 Found
Date: Sat, 26 Jun 2004 04:27:38 GMT
Server: Apache/1.3.28 (Unix) PHP/4.3.2
Content-Type: text/html; charset=iso-8859-1
Connection closed by foreign host.
Or use 'php -v'
PHP 4.3.1 (cgi), Copyright (c) 1997-2002 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2002 Zend Technologies
with the ionCube PHP Accelerator v1.3.3r2, Copyright (c) 2001-2002, by Nick Lindridge
> and Apache2 (mod_perl/1.99_09 Perl/v5.8.1 auth_mysql/1.11
> mod_ssl/2.0.47 OpenSSL/0.9.7b PHP/4.3.2). I have several questions
> about installing PhpWiki, and this mailing list seemed the best place
> to ask them. So:
> 1. When I extracted the tarball, the files all had user id of 1000 and
> group id of 513. I have no such user or group ids defined on my
> system. Are these just standard ids for PhpWiki, or do I have a
> problem? If the former, what would be some good names to assign to
> those numbers? If the latter, what needs to be fixed?
What user and group does your webserver run as? Use something like:
$ ps -e -o euser,egroup,pid,ppid,args | egrep httpd
root root 1064 1 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL -D STATUS
wwwrun nogroup 1178 1064 /usr/sbin/fcgi- -f /etc/httpd/httpd.conf -D SSL -D STATUS
wwwrun nogroup 1190 1064 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL -D STATUS
wwwrun nogroup 1700 1064 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL -D STATUS
showing that this webserver runs as user wwwrun, group nogroup.
To fix, go to the root of the phpwiki directory and do
$ chown -R wwwrun:nogroup .
substituting in the user and group that your webserver runs as. You will
probably need to do this as root (via sudo, etc...)
> 2. I installed MySQL for use with PhpWiki. I followed the installation
> guide and part of the tutorial for MySQL; it appears to be running
> fine. INSTALL-mysql tells me to edit index.php's $DBParams -- but
> there's no mention of it in my index.php! Grepping for "DBParams" show
> that it appears in several lib files, SOAP.php and wiki, but not in
> index.php. What happened?
The docs don't reflect the current code.
My guess is that you want to change database type in
./config/config.ini. This is not obvious.
find . -type f -print | xargs egrep -i '\$DBParams\[.dbtype.\] = '
./lib/IniConfig.php: $DBParams['dbtype'] = @$rs['DATABASE_TYPE'];
./lib/IniConfig.php: $DBParams['dbtype'] = 'dba';
./wiki://$DBParams['dbtype'] = 'SQL';
and poking in ./lib/IniConfig.php gives a link to
./config/config-default.ini; poking in ./index.php gives a link to
./config/config.ini. Without a lot of rummaging, you wouldn't have found
> 3. Supposedly PhpWiki works out of the box -- but what directory
> should I set this box in? :) I installed Apache2 so I could use
> PhpWiki, thus I'm new to Apache as well. I do have it set up and
> successfully serving regular HTML pages (via router port forwarding,
> if that matters to PhpWiki). Do I just drop the whole phpwiki-1.3.10
> directory into /var/www and cross my fingers? If Apache already has
> PHP support, do I have to do anything special to turn it on so that it
> executes PHP pages?
Look for a basic tutorial on PHP and read through your Apache
configuration file. Make a file consisting of the line '<?php phpinfo();
?>' and make sure it's readable by the webserver. If you can get that
file to display correctly (giving you way too much info about PHP), you
can put the phpwiki directory there and start using it (see above for
changing file ownership.)
I usually put the files outside the docroot and tell Apache where to
find them using the Alias and Directory directives but putting the
directory under the docroot should work as well.
Welcome to the learning curve! :)