Hi all,
In recent days several people asked me how is the work on instiki-ar
branch getting on. It is getting on fairly well.
By now, we have a version that seems quite fast enough for a small wiki
(say, upto 100-200 pages). We also have a conversion script that can
port the contents of all revisions from Madeleine storage into the wiki.
Issues that need to be addressed before we can release it are:
1. At least one know critical problem with the [[!include]] tag try to
include a page with any WikiLink on it, and see how it doesn''t work.
Once this is fixed (and some more testing is performed), instiki-ar
should become a usable software. We are probably just a few days away
from this point now!
2. Storing cached fragments in database. Shouldn''t be too difficult, we
just didn''t quite get to it yet.
3. Some other optimizations (such as caching web and web.pages for the
duration of request, doing something about Web#has_page?(name) method,
which gets called very often and makes a roundtrip to the database on
every call).
4. A sizable effort is still required on prepackaging Instiki with
SQLite for all supported platforms (to observe the No Step Three dogma).
5. Deployment on Lighttpd and Apache needs to be tested and sorted out.
6. More testing, including scalability for large wikis (e.g.,
http://rubyonrails.com)
If you want SQL-based Instiki to happen sooner than later, please look
into one of the issues listed above. A prompt fix for the Include bug
would be particularly apreciated (I wont have time to work on it untill
weekend myself).
To run the conversion script:
1. Put the particulars of your databases into config/database.yml
2. Execute script/create_db to create the database objects (tables and
indices)
3. Execute script/import_storage (do "ruby script/import_storage -h"
for
te list of options)
4. Logon to the database and run the SQL script created by import_storage
Remember that "instiki -e development" does not cache anything, and
reloads a lot of source files before each request - as opposed to
"instiki -e production" which caches a lot of things, including almost
all rendered pages.
Best regards,
Alex