hoodwink.d enhanced


Where is the Public Ruby Wikiware? #

by why in inspect

I wasted way too much time setting up the MouseHole wiki last week. The thing is: I really wanted to use a Ruby wiki. But I wanted to run the wiki on Rubyforge’s Apache setup. I could only find WEBrick instructions for Instiki and Soks. LesserWiki would be neat, but bootstrapping all the Rails libs and running through normal CGI would be time-consuming, slow, bad.

Just to illustrate how far I went with this, I ultimately got Viki, a Japanese-born Ruby-blooded wiki, to come up okay. See? Unfortunately, I can’t decipher the docs well enough to figure out the authentication scheme and there’s alot of code in there.

I’ve concluded that the most versatile public wiki is Batsman’s. Can it be?

said on 08 Sep 2005 at 15:11

Yeah, I wonder what it would take to put a file backend on Instiki.

said on 08 Sep 2005 at 15:24

I was just thinking about this today. I reckon Ara T. Howard’s acgi library announced on ruby-talk yesterday might be just the thing for getting soks to work through cgi, so watch this space…

said on 08 Sep 2005 at 16:05

instiki is in the middle of a transition to active record actually. i did the grunt work of getting it running (on lighttpd and sqlite). Just need to find the time to optimize a bit. Madeleine’s (Instiki’s old backend) idea of searching consisted of looping through every single page in memory. Anyone care to take this on? Here’s the dev branch.

said on 08 Sep 2005 at 17:03

Have you looked at Ruwiki?

said on 08 Sep 2005 at 17:07

I think a better question is, “Where is the winkware?”

said on 08 Sep 2005 at 19:49

The state of Ruby-wikidom is certainly not where it should be. We’ve fallen behind. It’s a tragedy that some Ruby projects have to run Python-based Wikis. It’s like we’re buying our satellites from the Soviets, people!

Will the new additions to Instiki to make it DB based instead of Madeline based help? Maybe. What about Hieriki? Anyone tried it? Seems to have some promising features. I’d really like to see a wiki that’s based on a plug-in architecture.

said on 08 Sep 2005 at 20:34

Surely Viki makes up for all its flaws with this!

said on 08 Sep 2005 at 22:52

the name of our new wiki. or perhaps sputniki. or maybe sputwinki.

Winki, that’s it! A whole new category! The name preceeds the idea. There’s a name, now what does a Winki do?

said on 08 Sep 2005 at 23:14

Oh, come on. A winki’s gotta be a domain that’s all blank pages.

said on 08 Sep 2005 at 23:14

How about Hiki? http://hikiwiki.org/en/

said on 09 Sep 2005 at 03:18

I second the Hiki suggestion. It has lots of nifty features, plugin support, authentication, and it should run fine as a cgi (since it is used for some sourceforge projects, i.e. ruby-gnome2)

said on 09 Sep 2005 at 04:46

Well. I think Instiki over-reached and we’ve been suffering ever since.

Okay, someone build a Ruby wiki, but forget about the Instiki prior art.

said on 09 Sep 2005 at 05:05

At the very least, forget about Instiki’s way of handling diffs.

Something more like Wikipedia’s way of handling changes would be wonderful.

said on 09 Sep 2005 at 07:28

Ruwiki is a good wiki, but is in bad need of someone to maintain it whose time isn’t eaten up by other projects, like PDF ::Writer.

I haven’t intended to abandon Ruwiki, and I still don’t, but I don’t see being able to get back to it for a few months yet.

said on 09 Sep 2005 at 10:10

Just don’t use my Nanoki please, thank you.

said on 09 Sep 2005 at 13:07

When’s the next Rails day, anyway? I’m sure a talented band of beer-fueled misfits could sew together a Ruby-tastic wiki in the time it takes a cartoon fox to wink.

said on 09 Sep 2005 at 16:03

Consider using Spark .

said on 10 Sep 2005 at 03:36

A way to handle diffs: prcs.sf.net (project revision control system).

said on 11 Sep 2005 at 19:05

What I’d really like to see is a wiki that stores its data as all flat files like Soks, but then has a database to acellerate the rendering. I’ve lost entirely too many hours recovering data from borked PHP Wiki databases to trust any SQL with an entire wiki. It would be great if there were a standard format for saving the revision control information between wikis, then the wiki software would be independant of the data and you could change software by just copying a directory.

said on 22 Sep 2005 at 19:43

Just installed the previously mentioned Hiki. The install was easy and it seems pretty nice.

said on 26 Sep 2005 at 08:22

Yeah … I’ve been fooling with Instiki and I must say it’s rather brittle. I think it will get better, but so far, I haven’t found a Rails wiki yet that I’d want to put up on my web site.

But then again … what’s wrong with using a Perl, Python, PHP , Java or C/C++ or Lisp or Fortran or whatever language tool if it does exactly what you want? Why do we need Rails wikis? Why do we need Rails blogs? Why do we need the Rails equivalent of phpBB? Why build a CRM /ERP system in Rails when there are good ones already?

Instead, let’s focus our creativity on building new tools for new jobs. In other words, write the next killer app in Rails, don’t rewrite last year’s Python killer app in Rails.

Comments are closed for this entry.