[Mediawiki-l] I just don't get the apache setup

[Arthur Guy]

This is what I have and it works fine
The Wiki is in the directory D:/htdocs/wikiav/w/

Virtual host settings:
Alias /wiki/skins     D:/htdocs/wikiav/w/skins
Alias /wiki           D:/htdocs/wikiav/w/index.php

Local host settings:
$IP = "D:/htdocs/wikiav/w";
$wgScriptPath	    = "/w";
$wgScript           = "$wgScriptPath/index.php";
$wgRedirectScript   = "$wgScriptPath/redirect.php";
$wgArticlePath      = "/wiki/$1";
$wgStylePath        = "$wgScriptPath/skins";
$wgStyleDirectory   = "$IP/skins";

I originally had trouble with the ScriptPath setting but when I got that
(trial and error) it all worked fine

Arthur Guy

arthur at astarsolutions.co.uk
www.astarsolutions.co.uk
 
--------------------------------------------------
For immediate online Audio and Video advice why not checkout WikiAV, our
Audio & Video Wiki Guide
www.wikiav.com
 

-----Original Message-----
From: mediawiki-l-bounces at Wikimedia.org
[mailto:mediawiki-l-bounces at Wikimedia.org] On Behalf Of Rick DeNatale
Sent: 13 July 2005 20:20
To: MediaWiki announcements and site admin list
Subject: [Mediawiki-l] I just don't get the apache setup

I've just moved from Redhat to Ubuntu. I'm now using Apache2.  I got
wiki to where it was working without any rewriting and using url's of
the form

http://www.mercuryspacecraft.com/wiki/index.php/Main_Page

I had it installed in the wiki subdirectory of the virtual hosts document
root

I then tried to once again "prettify" the urls, and to separate w from
wiki as described in
http://meta.wikimedia.org/wiki/Eliminating_index.php_from_the_url
Using the Alias statements instead of rewrite rules

Now I can't make it work.  I'm confused as to where I want to name the
physical install path, should it be w or wiki. Since the Aliases seem
to be going from /wiki... to /installpath/w...  I think that it should
be in /var/www/w which is where I've put it.

THe only thing which semi works is if I use a url like
http://www.mercuryspacecraft.com/index.php/Main_Page

but thats broken, it looks like it isn't getting the style sheets.
The Apache error log contains:
[Wed Jul 13 15:04:07 2005] [error] [client 166.82.49.174] File does
not exist: /var/www/wiki, referer:
http://www.mercuryspacecraft.com/w/index.php/Main_Page

Here's what I have in my Virtual server:

<VirtualHost *>
        ServerAdmin webmaster at mercuryspacecraft.com
        ServerName www.mercuryspacecraft.com
        DocumentRoot /var/www
        AcceptPathInfo on

        Alias /wiki/stylesheets /var/www/w/stylesheets
        Alias /wiki/style /var/www/w/style
        Alias /wiki/images /var/www/w/images
        Alias /wiki/skins /var/www/w/skins
        Alias /wiki/redirect.php /var/www/w/redirect.php
        Alias /wiki/textvc.php /var/www/w/textvc.php
        Alias /wiki/index.php /var/www/w/index.php
        Alias /wiki /var/www/w

</VirtualHost>

And the relevant parts of my LocalSettings.php

$wgScriptPath       = "/wiki";
$wgScript           = "$wgScriptPath/index.php";
$wgRedirectScript   = "$wgScriptPath/redirect.php";

$wgArticlePath      = "$wgScript?title=$1";


Any  ideas?
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l at Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l




'a star solutions' disclaimer
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. 
If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited.
If you received this in error, please contact the sender and delete the material from any computer. 
Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the company.
We believe that this communication is free from viruses and other potentially dangerous programmes, but the recipient opens this communication at their own risk. 
We assume no responsibility for any loss or damage arising from the receipt or use of this communication