I'm wondering if there would be any interest in a Tiddlywiki container which serves one or more tiddlywikis with authentication & webdav enabled, so the wiki will save back in place over itself on the server when updated.
Mainly wondering because I just got part of this (minus authentication but that's later) working for myself with Apache on a Turnkey core image. And it seems conceptually pretty simple, and perhaps less complex for a first image than some of the others I still have on my list (LEPP, Pleroma, etc).
I would be doing this by enabling the Apache userdir mod to serve ~/public_html, and modify /etc/apache2/mods-available/userdir.conf to enable WebDAV.
I'm curious if anyone has thoughts about the fact that currently, once a wiki is modified and saved, it lands in ~user/public_html/wikiname.html with user and group both set to www-data. Might be nicer to have it owned by the user.
My thought in doing it all this way is that it takes advantage of basic Linux mechanisms to be multi-user (just create accounts and create ~/public_html, and stick a tiddlywiki copy in... maybe could be done by skel) ... and then backup, sharing, etc of a stable of tiddlywikis (should one ever have such a thing) becomes as easy as using standard utilities to deal with everybody's public_html.
Anyway, Tiddlywiki is great in its niche (a fully functional wiki in a single .html file) but serving & saving changes has always been its Achilles heel due to the browser security model. Anything that helps that (like a Turnkey image which serves up Tiddlywikis) is a good thing.
