From: Alan Chen <alan@...>
Date: 2002-12-03T08:27:11+09:00
Subject: Re: MiniRubyWiki has struck again

On Tue, Dec 03, 2002 at 07:43:55AM +0900,  JamesBritt wrote:
> > Yes because it's 600 lines of code and (in my exalted opinion) easy to
> > morph.
> 
> So I've found.  I hacked an earlier version so that it could run on a public
> server where I cannot run the code with its own web server.
> 
> >
> > No because it disregards all CGI except some filters, and does
> > not push or
> > pop data into environmental variables. Hence one would need to start
> > somewhere above the level of getFile() to graft to CGI.
> >
> > You could move your apache to 8080 and give MWR the default 80 port. ;-)
> 
> Well, no.  It's not my Apache.  There is a great value in a Ruby-based Wiki,
> but tight coupling with a built-in server is a problem for me, and perhaps
> others, who just want to set up a site on a 3rd-party ISP.
> 
> Might be the motivation to go write my own ...
> 
> James

I've got a very minimal ruby wiki working that's getting close to
releasable. Right now I'm calling it RuWiki. (Roo-wicky or Roo-icky)
It features basic wiki markup, setup for plain CGI access, and has a
pluggable storage backend - right now only flatfile storage is
implemented, a postgreSQL or mySQL backend will be implemented after
the first release. I'm about to embark on implementing "fallback" page
templating (later I want to go to amrita) and do a little cleanup for
an initial release.

It does have some experimental code in it for playing around with wiki
Project namespaces -- identical topic names won't collide if they're
in different projects. To use RuWiki as a regular wiki, you just stay
in the Default project namespace. Project namspaces are only partially
complete. You can access, edit, and store in different projects, but I
haven't decided on how to markup "cross-project" namespace references
yet.

-- 
Alan Chen
Digikata Computing
http://digikata.com