Hi Mario, thank you for elucidating!
On Wednesday, May 28, 2014 11:00:10 PM UTC+2, PMario wrote: > I did several experiments with a "vanilla" tiddlyweb installation ... > combining it with TWclassic [2]. > I also tried to create a "1 click" setup with the help of vagrant and > VirtualBox, to make experiments easier. .. But this configuration doesn't > work well with TW5 out of the box. > Okay, I'm staying away from TWC as I would have to spend some time on learning how to use it. Also it seems pointless to put time and effort into it as I have no existing project that needs a conversion to TW5, although I'm sure that TWC still has it's advantages. The way I see it I'll have to start experimenting with a vanilla TiddlyWeb installation and the incomplete TW5 storage module and then I'll hopefully see what needs to be done. > IMO TW5 needs a different approach, which is pretty straight forward. > nginx + wsgi + tiddlyweb, where nginx serves a "lazy" TW5.html file ... As > above the TW5 adapter isn't finished yet. > Is there a strict dependency on nginx or is it just the default web server used with TiddlyWeb. Is running Apache+mod_wsgi not recommended? >> TiddlyWeb has some server side plugins, that could do indexing, that can >>> be accessed with a query string in the URL. >>> >> >> That's great! Does this work already with TW5? >> > > That's independent from TW5. I was thinking about the server side whooser > plugin [4]. TW5 has no UI to use this function. > Indexing also depends on your tiddler store. So if you use the file store, > or a sql database. Which increases the number of moving parts .... > I know that there is no UI. What I'm still trying to figure out is how low-level the integration of a server-side store can be implemented, i.e. whether it's possible to directly pass queries on to the store so that for instance when a user requests the "References" or "Tagging" fields of a tiddler a backend query is issued requesting information about connections of this tiddler. Is this a categorical thing, i.e. does the core of TW or TiddlyWeb need >> major adjustments to the core? >> > Or is it only the glue that's missing, i.e. api calls and filling various >> hooks and callbacks? >> > You need to do the server side configuration right. > Have you tried it? If your TW is too big, you can split it into several TWs, so every file has > less tiddlers. IMO splitting a TW is much less work than dealing with the > server side. > But if you want multi user TWs imo you'll need a server side. > For the time being my TWs are not to big, but they grow fast. I don't like splitting it into different wikis, because I don't like the idea of a single file containing all data and also there is no satisfactory way to link between wikis. Stefan, you have an gmx.at acount. So where are you from? > >From the city built around the river mur :) You? Stefan -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
