On Tue, 2003-03-18 at 12:10, Lee Daniel Crocker wrote:
(Michel Mouly
<mmouly(a)wanadoo.fr>)r>):
wikipedia : the last versions of the files found on source forge,
loaded one by one (how to dump the CVS??)
Get an account on Sourceforge. Install CVS (I have no idea how to
do this for Windows). Then use:
Supposedly there's a program 'WinCVS' which has a windows interface that
some people use. As a unix-head, I just run Cygwin and use the
unix-style tool. :)
> I tried to run rebuildindex.php, but it aborts,
seemingly some
> timer in the server (message is an overload indication). Is there
> any way to do that without invoking the server? For instance, a
> MySQL script would be handy!
PHP generally has an execution time limit (default is 30 seconds I
think). This makes sense for web stuff which should generally never take
that long, but is obviously not something you want for your admin
scripts which might take an hour or two for really big things.
I run these scripts from the command line:
php rebuildIndex.php
This avoids the timeouts, gives me regular job control (well, under
Unix), and most importantly does not require the maintenance scripts to
be web-accessible!
Make sure your PATH is set appropriately, or use the full path to the
php executable, ie:
c:\webserver\php\bin\php rebuildIndex.php
(or something like that? I've never run these things on Windows, I
always use Linux for my servers.)
Hmm. Yes, if you load pages through SQL, you have to
rebuild the
indexes again. Maybe the French SQL dump was in an old format?
Brion?
It should be current... As a reminder, the SQL dumps only include the
'cur' and 'old' tables. The link, recentchanges, and search index tables
are recreated by the rebuild scripts:
rebuildLinks.php does links, recentchanges
rebuildIndex.php does search index.
These, I think, rely on the tables already existing, so you should run
the createdb.php before importing the data. (Michel I think is already
doing this part right.)
Hmm, it occurs to me that we don't have a clean backup/rebuild system
for the uploads. Probably someone should look into that.
> d) When I edit a page, the submit yields a blank
page after a long
> time. Likely to be a pb in the php scripts, but this seems beyond
> my competence.
No idea...
e) After a
submit on a new page, I can see the modification only
after deleting the IE cache and recalling wiki.phtml. I set the
browser to checking most recent version at each page download, but
the behaviour is the same.
Got me there. I'm afraid I can't be much help for Windows.
IE has the crappiest reload button ever, in that it doesn't reload
unless you hold down control. Help with workarounds for this is
welcome...
In all honesty, though, I don't think the
Wikipedia software is
really good for personal use.
I do agree. There hasn't been a public, packaged, numbered software
release for a reason: it's idiosyncratic, built for a single site, has a
lot of assumptions (like all those hard-wired strings talking about
Wikipedia and GNU FDL license for text!), and way overkill for most
purposes.
I'm not going to say, "don't use it!" But keep the same caveats that
you
would have for an early pre-alpha release of any large application with
a lot of weird features. It's fragile, and if you're trying to get real
work done it might not be for you unless you're willing to put a lot of
effort into it.
There are a lot of smaller, simpler
Wikis that do a great job--I use UseMod for my personal site,
for example. I really wrote this one for one and only one goal:
to run Wikipedia. If it's useful for other things,I certainly don't
mind, but that's not a goal I ever had.
UseMod is also fairly easy to set up -- one perl script. :D
-- brion vibber (brion @
pobox.com)