-----Original Message-----
From: instiki-users-request@rubyforge.org
Date: Sat, 30 Jul 2005 20:52:51
To:instiki-users@rubyforge.org
Subject: Instiki-users Digest, Vol 3, Issue 5
Send Instiki-users mailing list submissions to
instiki-users@rubyforge.org
To subscribe or unsubscribe via the World Wide Web, visit
http://rubyforge.org/mailman/listinfo/instiki-users
or, via email, send a message with subject or body ''help'' to
instiki-users-request@rubyforge.org
You can reach the person managing the list at
instiki-users-owner@rubyforge.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Instiki-users digest..."
Today''s Topics:
1. Re: Pluggable Storage Implementations? (zer0halo)
2. Re: I''m still alive (Alex Verhovsky)
3. Re: Delete a Wiki (Assaph Mehr)
4. Re: I''m still alive (Assaph Mehr)
5. Re: I''m still alive (David Rosam)
6. Re: I''m still alive (David Guest)
7. [ANN] Instiki 0.10.2 (Alex Verhovsky)
8. Instiki.org is back and upgraded to 0.10.2 (Alex Verhovsky)
----------------------------------------------------------------------
Message: 1
Date: Fri, 29 Jul 2005 14:34:27 -0600
From: zer0halo <zerohalo@gmail.com>
Subject: Re: [Instiki] Pluggable Storage Implementations?
To: Instiki-users <instiki-users@rubyforge.org>
Message-ID: <92b38bd505072913342cac37f8@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 7/29/05, Tam?s Smith <tamassmith@mac.com> wrote:
> I think we should make Instiki''s data storage method pluggable.
I agree. Allows for greatest flexibility.
> Use the
> current Madeleine method as the initial implementation.
Yes and No. The beauty of madeleine is that is makes interacting with
the wiki fast, and it requires no user setup.
The disadvantage of Madeleine is that if anything goes wrong with your
wiki - and the law of averages is that something will go wrong
sometime - you could be denied access to all your data, unless you
figure out a way or write something to extract it from your snapshot
and recreate it. It happened to me: I must have put something in a
page that Instiki didn''t like, I got the "Rails application
error" and
that was it. A new installation of Instiki with the snapshot copied
over rendered the same result. Fortunately I was just starting the
wiki. But if that happens to a user with a full-blown wiki and not
only their wiki crashes but they can''t access all the data in it, you
can imagine their reaction.
Of course you could export to Textile or HTML every day to avoid that,
but users don''t want to be burdened with that.
> I would prefer a file system storage implementation where each page
> gets a directory. The current revision exists as a plain-text textile
> file in that directory. Diffs, also plain-text files in the directory,
> give you the ability to patch back to the initial revision.
>
> Place any file uploads for that page into the same directory. On that
> page, allow use of simple filename for either image display or download
> link of one of these uploaded files.
>
I agree. DokuWiki (http://wiki.splitbrain.org/wiki:dokuwiki) uses a
file system implementation and it works well. It''s a bit slower of
course than using a database, but it has two huge advantages:
- Easy data accessibility and manupulation outside the wiki. Want to
move a section of your wiki somewhere else, or even to its own wiki?
No problem, just move the folder (all the links within that folder
will still work with each other.)
- Want to rename a page? Easy, just rename the file.
- Your wiki crashes and you can''t get it working? The data is still
nicely in your files. You can still read it easily since it doesn''t
store it in the converted HTML but the original markup format.
DokuWiki supports namespaces (something that would be very nice to
have in Instiki), and uses folders to represent those namespaces. I
think that''s a good idea to implement as well.
In DokuWiki, each wiki page in that namespace is a file in that
folder. I would argue that might be simpler than each page having its
own folder. Rather all of the pages under a namespace would be located
in that folder. Any attachments attached to pages in that namespace
would also be in that same folder. (There would be a "default" folder
for pages/attachments not assigned to a namespace.)
That would allow the user to reference an attachment from any page in
the namespace by simply placing the file in the namespace folder
(either through an simple Instiki web interface or via FTP transfer or
however they want to do it). If you want to link to an attachment
that''s in another namespace you just reference it by
namespace:attachment or similar syntax.
You could also easily have an "Attachments" link that would show all
of the attachments grouped by namespace, in case you want to locate
one in particular without knowing what page is referencing it. This
would be a simple folder listing of all files (except the page files
themselves) in your folder structure.
It''ll also make it easy to implement access control to certain
namespaces or pages simply by restricting access to those folders or
files.
Of course all of this could be acheived through mysql as well--and
mysql would allow for even more possibilities and be faster. But this
way the user doesn''t have to install mysql.
Well, those are some ideas to get the discussion flowing.
--
"Impossible is nothing."
------------------------------
Message: 2
Date: Fri, 29 Jul 2005 19:52:42 -0600
From: Alex Verhovsky <alex@verk.info>
Subject: Re: [Instiki] I''m still alive
To: zer0halo <zerohalo@gmail.com>, Instiki-users
<instiki-users@rubyforge.org>
Message-ID: <42EADD6A.5000700@verk.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
zer0halo wrote:
>Are you thinking of Instiki using mysql instead of Madeleine for data
>storage? IMO, that would be a great improvement and allow for greater
>flexibility of future development and add-ons.
>
>
MySQL shall be supported. SQLite is being mentioned as a way to retain
the ease of installation; which is darn useful for personal or small
project wikis. MySQL would be for web sites (eg, instiki.org).
Basically, there is a desire to make an ActiveRecord backend, thus
completing transformation of Instiki into a textbook Rails application.
Re pluggable backend. It sounds cool. Madeleine sounds cool... but in
practice it''s a pain in the stern. I''m inclined to think that
we "aint
gonna need it". Similar story with file system storage - sorry guys, but
it is not what I want to do right now.
Best regards,
Alexey Verkhovsky
------------------------------
Message: 3
Date: Sat, 30 Jul 2005 17:17:14 +1000
From: Assaph Mehr <assaph@gmail.com>
Subject: Re: [Instiki] Delete a Wiki
To: dpguest@bestweb.net, Instiki-users <instiki-users@rubyforge.org>
Message-ID: <3ff47be90507300017661d8267@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 7/29/05, David Guest <dpguest@bestweb.net>
wrote:> Is there any way to delete one of several wiki''s on a wiki site?
Not through the web interface. If you don''t mind a bit of hacking look
at:
http://rubyforge.org/pipermail/instiki-users/2005-May/000076.html
HTH,
Assaph
------------------------------
Message: 4
Date: Sat, 30 Jul 2005 18:20:32 +1000
From: Assaph Mehr <assaph@gmail.com>
Subject: Re: [Instiki] I''m still alive
To: Instiki-users <instiki-users@rubyforge.org>
Message-ID: <3ff47be905073001205d278b65@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
> But finally, I''m back with you.
Glad to have you back!
> ...and then we want to try and give Instiki a real SQL backend.
ooh boy :-)
Cheers,
Assaph
------------------------------
Message: 5
Date: Sat, 30 Jul 2005 10:59:44 +0100
From: David Rosam <davidrosam@gmail.com>
Subject: Re: [Instiki] I''m still alive
To: Instiki-users <instiki-users@rubyforge.org>
Message-ID: <574dd6ff05073002593da21958@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Alexey
Can I give my $0.02 as a user not a hacker?
What attracted me to Instiki (and then to Pimki) was the ease of
installation for its feature set, so please make sure Instiki doesn''t
become
JAHW (just another heavyweight wiki!) that will require me tangling with
lots of extra technology - SQLite (whatever that is) sounds encouraging.
Cheers
David
On 7/30/05, Alex Verhovsky <alex@verk.info> wrote:>
> zer0halo wrote:
>
> >Are you thinking of Instiki using mysql instead of Madeleine for data
> >storage? IMO, that would be a great improvement and allow for greater
> >flexibility of future development and add-ons.
> >
> >
> MySQL shall be supported. SQLite is being mentioned as a way to retain
> the ease of installation; which is darn useful for personal or small
> project wikis. MySQL would be for web sites (eg,
instiki.org<http://instiki.org>
> ).
>
> Basically, there is a desire to make an ActiveRecord backend, thus
> completing transformation of Instiki into a textbook Rails application.
> Re pluggable backend. It sounds cool. Madeleine sounds cool... but in
> practice it''s a pain in the stern. I''m inclined to think
that we "aint
> gonna need it". Similar story with file system storage - sorry guys,
but
> it is not what I want to do right now.
>
> Best regards,
> Alexey Verkhovsky
>
> _______________________________________________
> Instiki-users mailing list
> Instiki-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/instiki-users
>
--
David Rosam
IT and SEO copywriting
davidrosam@gmail.com http://dangerous-thinking.com
+44 (0)70 440 ROSAM (76726) Skype:davidrosam
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/instiki-users/attachments/20050730/194913df/attachment-0001.htm
------------------------------
Message: 6
Date: Sat, 30 Jul 2005 06:50:45 -0400
From: David Guest <dpguest@bestweb.net>
Subject: Re: [Instiki] I''m still alive
To: David Rosam <davidrosam@gmail.com>, Instiki-users
<instiki-users@rubyforge.org>
Message-ID: <42EB5B85.1020001@bestweb.net>
Content-Type: text/plain; charset="iso-8859-1"
David Rosam wrote:
> Hi Alexey
>
> Can I give my $0.02 as a user not a hacker?
>
> What attracted me to Instiki (and then to Pimki) was the ease of
> installation for its feature set, so please make sure Instiki
doesn''t
> become JAHW (just another heavyweight wiki!) that will require me
> tangling with lots of extra technology - SQLite (whatever that is)
> sounds encouraging.
>
>
>
Boy, do I second that opinion....KISS
However, I use a database, NexusDB, very fast and S!L 2003 compliant ...
I''d love to be able to switch out mysql and use Nexusdb ... with an
easy
switch ....
>------------------------------------------------------------------------
>
>_______________________________________________
>Instiki-users mailing list
>Instiki-users@rubyforge.org
>http://rubyforge.org/mailman/listinfo/instiki-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/instiki-users/attachments/20050730/d1421067/attachment-0001.htm
------------------------------
Message: 7
Date: Sat, 30 Jul 2005 11:02:59 -0600
From: Alex Verhovsky <alex@verk.info>
Subject: [Instiki] [ANN] Instiki 0.10.2
To: Instiki-users <instiki-users@rubyforge.org>,
ruby-talk@ruby-lang.org, rails@lists.rubyonrails.org
Message-ID: <42EBB2C3.6020403@verk.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Dear all,
Coming back from a long hibernation over Microsoft .NET textbooks, I
have just released Instiki 0.10.2.
Instiki is a Wiki Clone <http://www.c2.com/cgi/wiki?WikiWikiClones>
that''s so easy to set up and so pretty to look at, you''?l be
wondering whether this is a real wiki at all.
It is also the most frequently downloaded end-user application on RubyForge,
surpassed only by the Ruby One Click Installer and RubyGems.
0.10.2 is a maintenance release. Primarily it is about fixing the "endless
redirects loop, triggered by a RedCloth exception" bug. Here is the full
list of changes in the version:
* Resolved the "endless redirection loop" condition and otherwise
improved handling of errors in the rendering engines
* Fixed HTML export
* Upgraded to Rails 0.13.1
* Added layout=no option to the export_html action (it exports page contents
processed by the markup engine, but without the default layout - so that they
can be wrapped in some other layout)
* <nowiki> tag can span several lines (before it was applied when both
opening and closing tags were on the same line only)
* Fixed rendering of Markdown hyperlinks such as
[Text](http://something.com/foo)
The released files are available at http://rubyforge.org/frs/?group_id=186
Online documentation is at http://instiki.org (the site is down as I write this,
but it will be back soon).
Source code and bug tracker are at http://dev.instiki.org
An updated gem is already available on RubyForge gem server.
Best regards,
Alexey Verkhovsky
------------------------------
Message: 8
Date: Sat, 30 Jul 2005 18:58:04 -0600
From: Alex Verhovsky <alex@verk.info>
Subject: [Instiki] Instiki.org is back and upgraded to 0.10.2
To: Instiki-users <instiki-users@rubyforge.org>
Message-ID: <42EC221C.9060004@verk.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi all,
http://instiki.org site is back up and upgraded to 0.10.2. I''m
fervently
hoping that it stays up, but <tester hat on/> who knows... <tester hat
off/> :) Anyway, if you see any problem with the upgraded wiki, in the
next week or so, don''t bother with Trac tickets, just email me about
it.
I''ll try to fix it as fast as possible.
Also, I am planning some major refactoring of the wiki content in the
coming days - removing old revisions, obsolete pages etc. The objective
is to make it more relevant to the current version, better structured
and (most importantly) smaller and easier on the memory.
Best regards,
Alex
------------------------------
_______________________________________________
Instiki-users mailing list
Instiki-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/instiki-users
End of Instiki-users Digest, Vol 3, Issue 5
*******************************************
(mobile)