On Dec 14, 2004, at 3:04, Brian Lalor wrote:
I'm cc'ing the mailing list for this one.
A note I made atop the XSLT node and my entire [[Brian Lalor]] node have been nuked. Should I take it personally? Perhaps it's time to implement a more robust wiki, a la Confluence ($$) or SnipSnap?
David finally found the time to merge the rollback patch into instiki but in the process zapped all pages from after november the 5th (apologies on his behalf for not updating the wiki with this info).
I have a backup of all the current pages, so they are not lost -- but there is no easy way to import them, so I do think this is the chance to move to another wiki.
I have no experience with other wiki software, a few things that would be nice: o run under apache (to allow for robots.txt and fine-masked authentication) o some wiki-spam prevention o page history with rollback of course ;) o would be preferable if the syntax is textile for compatibility o and preferable also if it can import pages easily
If there are any suggestions, it would be nice to know how they fit with the above requests.
On Dec 13, 2004, at 9:32 PM, Allan Odgaard wrote:
I have no experience with other wiki software, a few things that would be nice: o run under apache (to allow for robots.txt and fine-masked authentication) o some wiki-spam prevention o page history with rollback of course ;) o would be preferable if the syntax is textile for compatibility o and preferable also if it can import pages easily
If there are any suggestions, it would be nice to know how they fit with the above requests.
I've played a fair bit with SnipSnap[1], and in fact have one running[2] on my Fedora box at home if anyone wants to play. Registration is open for the time being. If anyone wants admin rights, I'll set you up.
Confluence[3] abso-freaking-lutely *rocks*, but costs about $4kUSD. Too bad TM isn't open source, 'cause they do OS licenses for free. ;-)
Confluence uses a Textile-similar markup language, and it would not be difficult to extend SnipSnap to use JTextile. From what I've seen, instiki isn't "pure" Textile, so any kind of import will require work.
[1] http://snipsnap.org/ [2] http://telly.bravo5.org/snipsnap/space/start [3] http://confluence.atlassian.com/
On 14-déc.-04, at 03:32, Allan Odgaard wrote:
On Dec 14, 2004, at 3:04, Brian Lalor wrote:
I'm cc'ing the mailing list for this one.
A note I made atop the XSLT node and my entire [[Brian Lalor]] node have been nuked. Should I take it personally? Perhaps it's time to implement a more robust wiki, a la Confluence ($$) or SnipSnap?
David finally found the time to merge the rollback patch into instiki but in the process zapped all pages from after november the 5th (apologies on his behalf for not updating the wiki with this info).
I have a backup of all the current pages, so they are not lost -- but there is no easy way to import them, so I do think this is the chance to move to another wiki.
I have no experience with other wiki software, a few things that would be nice: o run under apache (to allow for robots.txt and fine-masked authentication) o some wiki-spam prevention o page history with rollback of course ;) o would be preferable if the syntax is textile for compatibility o and preferable also if it can import pages easily
If there are any suggestions, it would be nice to know how they fit with the above requests.
For me, it's a bit sad that you're moving to another wiki, as it's Instiki that lead me to Textmate... (Ruby -> Instiki -> LoudThinking -> TextMate). Too bad David doesn't have the time to work on Instiki anymore. It looks like this nice project is dying.
I'm still using Instiki as my (private) wiki, but before that I used pmWiki, it's written in PHP and has a lot of nice features. The only thing of your list it doesn't fit with is that it use it's own markup
-
Allan Odgaard -
Brian Lalor -
Fred B.