[CS-FSLUG] wiki for spawning ministry ideas

[Vincent Danen]

* Micah Yoder <yoderm at gmail.com> [2007-12-19 14:51:47 -0600]:

>> The other nice thing about Mediawiki is it uses MySQL or PostgreSQL to
>> store the data.  TWiki uses flat files and rcs to handle version control
>> which is wildly inefficient.
>
>Wow, I didn't know it could work with PostgreSQL.  That would be a big
>selling point, as I was sort of hoping to keep MySQL off the server.
>:)

I don't think I've tried it with PostgreSQL, but it is supposed to work.

>Now if only it were in a language more efficient than PHP, which has
>to re-parse everything on every request, but like I said, for 2000
>hits a day, no problem.  And Wikipedia obviously proves it isn't that
>big a problem.

You can do caching.  There's actually a few different mechanisms you can
use from php object caching (using some pecl or other extensions), or a
file cache that you can invalidate as often or as little as you like.
People logged in will get the data pulled from the db while people not
logged in will get the cache (although the cache will get updated by
logged in people if they make changes to a page).

Mind you, your argument is no different than TWiki with perl (and
without mod_perl).  At least with PHP you can use a few different
caching mechanisms.

-- 
Vincent Danen @ http://linsec.ca/