A
Alex Verhovsky
Hi all,
We've got a working (at least to some extent) Instiki implementation
backed by an ActiveRecord backend and SQLite database. It's in a
Subversion branch http://svn.instiki.org/instiki/branches/instiki-ar/,
revision 360.
If you find yourself thinking "heck, so what?", one possible consequence
is that one day it will drastically reduce rubyonrails.org downtime and
increase its performance. Not to mention that all the people running
public Instiki instances will get the FastCGI deployment option most of
them are crying for. Besides, <hype>Instiki is the most popular end-user
application in the Ruby world</hype>
"Working to some extent" refers to the fact that it passes all available
automated tests (unit, functional and Watir), as well as half an hour of
random poking around, while running on WEBRick with SQLite DB, under
Windows XP. It probably will be heinously slow on any wiki larger than
~100 pages, so we are just half-way through the "make it work, then make
it fast" road. Still need to do performance testing, refactor the
database for speed, define indexes, implement some caching etc. In other
words, all the "wizardry" bits. So, I thought maybe I can get some
wizards with Rails production expertise interested to the point of
getting involved at this stage.
Even if you are not a wizard yet, you are most welcome to try it out and
tell me about the problems you encounter.
Best regards,
Alex
We've got a working (at least to some extent) Instiki implementation
backed by an ActiveRecord backend and SQLite database. It's in a
Subversion branch http://svn.instiki.org/instiki/branches/instiki-ar/,
revision 360.
If you find yourself thinking "heck, so what?", one possible consequence
is that one day it will drastically reduce rubyonrails.org downtime and
increase its performance. Not to mention that all the people running
public Instiki instances will get the FastCGI deployment option most of
them are crying for. Besides, <hype>Instiki is the most popular end-user
application in the Ruby world</hype>
"Working to some extent" refers to the fact that it passes all available
automated tests (unit, functional and Watir), as well as half an hour of
random poking around, while running on WEBRick with SQLite DB, under
Windows XP. It probably will be heinously slow on any wiki larger than
~100 pages, so we are just half-way through the "make it work, then make
it fast" road. Still need to do performance testing, refactor the
database for speed, define indexes, implement some caching etc. In other
words, all the "wizardry" bits. So, I thought maybe I can get some
wizards with Rails production expertise interested to the point of
getting involved at this stage.
Even if you are not a wizard yet, you are most welcome to try it out and
tell me about the problems you encounter.
Best regards,
Alex