summaryrefslogtreecommitdiff
path: root/doc/forum
diff options
context:
space:
mode:
authorhttp://schmonz.livejournal.com/ <http://schmonz.livejournal.com/@web>2009-08-02 10:22:39 -0400
committerJoey Hess <joey@kitenet.net>2009-08-02 10:22:39 -0400
commit81ad4377e90961a46d97248844f5fa7f26be3f24 (patch)
tree40ad5645a8edf00ef4c669514f0a06c0bd0085b0 /doc/forum
parent2ca129cb31c6cdc673674d454f2f749fba7eac6a (diff)
response
Diffstat (limited to 'doc/forum')
-rw-r--r--doc/forum/ikiwiki_over_database__63__.wiki20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/forum/ikiwiki_over_database__63__.wiki b/doc/forum/ikiwiki_over_database__63__.wiki
index ff123e98d..fb4d41763 100644
--- a/doc/forum/ikiwiki_over_database__63__.wiki
+++ b/doc/forum/ikiwiki_over_database__63__.wiki
@@ -1 +1,21 @@
Is there here any possibility to modifying ikiwiki (via plugin) for store pages in database. I'm thinking about storing pages in sqlite or mysql for serving it much faster. The idea is from sputnik.org [http://sputnik.freewisdom.org/] but with perl ;-). Could we integrate the sputnik code in ikiwiki as a solution?
+
+> ikiwiki generates static pages in a filesystem. It's responsible
+> for editing and regenerating them, but they're served by any old
+> web server. If you go to the trouble of stuffing the generated pages
+> into a database, you'll need to go to further trouble to serve them
+> back out somehow: write your own web server, perhaps, or a module
+> for a particular web server. Either way you'll have sacrificed
+> ikiwiki's interoperability, and it's not at all clear (since you're
+> adding, in the best case, one layer of indirection reading the
+> generated files) you'll have gained any improved page-serving
+> performance. If it's source pages you want to store in a database,
+> then you lose the ability to do random Unixy things to source pages,
+> including managing them in a revision control system.
+>
+> Static HTML pages in a filesystem and the ability to do random
+> Unixy things are two of the uniquely awesome features of ikiwiki.
+> It's probably possible to do what you want, but it's unlikely that
+> you really want it. I'd suggest you either get to know ikiwiki better,
+> or choose one of the many wiki implementations that already works
+> as you describe. --[[Schmonz]]