[pmwiki-users] Farms

Ben Wilson dausha at gmail.com
Thu Apr 12 11:28:02 CDT 2007


Not "index.html," as much as "index.php." I advocate the index.php
because many web servers expect to map to an index.* when given a
clean URL (e.g. http://www.example.org to
http://example.org/index.html).

Now that I have a web server of my own, I put PmWiki in
/usr/local/pmwiki and then:
  ln -sf /usr/local/pmwiki/pmwiki.php index.php

I also have /usr/local/share/pmwiki/(pub/cookbook) for that other
stuff. I symlink /pub to each field (I've not gotten past having to
have it in each field), but I have a farmconfig.php that maps $FarmC
to /usr/local/share/pmwiki/cookbook/; then
include_once("$FarmC/recipe.php");.

FWIW, I am running about a dozen totally distinct sites using PmWiki
in a farm configuration as lighted described above. My documentation
of how I do it is a bit obfuscated, as Pm has admonished me in the
past. So, if my approach is confusion it's not your fault. :-)

Ben

On 4/12/07, DaveG <pmwiki at solidgone.com> wrote:
>
> Correct. You would have an index.html that pointed to the pmwiki.php. Ben suggests pointing to the pmwiki.php using a synonym, which will make it easy to simply switch the synonym when upgrading/downgrading PmWiki versions.
>
> On Thu, 12 Apr 2007 14:35:45 +0200, Mark Trumpold <mark at ruthtrumpold.id.au> wrote:
> > So would I no have a pmwiki.php file in my other wikis but only in the
> > wikifarm engine?
> >
> >
> > On 12/4/07 1:29 PM, "DaveG" <pmwiki at solidgone.com> wrote:
> >
> >>
> >>
> >>
> >> On Thu, 12 Apr 2007 10:54:49 +0200, Mark Trumpold
> > <mark at ruthtrumpold.id.au>
> >> wrote:
> >>> Hi again
> >>>
> >>> After a little more reading I still have questions;-)
> >>> Do I install a new 'empty' or 'dummy' pmwiki that all the existing
> > wikis get
> >>> there scripts etc etc? The way I look at it it would make upgrading
> > easy
> >>> and safer (less risk to the existing Data. So if something were to go
> > wrong
> >>> with the dummy wiki the others would be still ok.
> >> That's the approach Ben Wilson documents on the FarmSetupByExample page.
> > I
> >> didn't take that approach yet simply because I already set things up
> > another
> >> way, but when I get some time I will likely switch. Logically having the
> >> PmWiki engine separate from all farm data (local, wiki.d) makes more
> > sense,
> >> and is less prone to errors when upgrading.
> >>
> >>> If I do that will it affect the wiki.d directory that has all my
> > valuable
> >>> pages? I read somewhere that it will make a new wiki.d for any wiki new
> > to
> >>> a farm. I don't mean new wiki but existing wiki joining the farm.
> >> In this type of setup you simply move the wiki.d to another directory.
> >> Essentially the wiki.d in the PmWiki engine directory will not be used.
> >>
> >> Whilst experimenting, simply make a backup copy of wiki.d. That way if
> >> something does get overwritten, you can simply copy it back.
> >>
> >>
> >>  ~ ~ Dave
> >>
>
>
> _______________________________________________
> pmwiki-users mailing list
> pmwiki-users at pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>


-- 
Ben Wilson
"Words are the only thing which will last forever" Churchill



More information about the pmwiki-users mailing list