Lost Admin
2017-08-24 13:53:17 UTC
A while back, Jeremy mentioned in another post
<https://groups.google.com/d/msg/tiddlywiki/cO8lYpmAMWE/bKc6mPRZBgAJ> that
TiddlyWiki supports saving via WebDav. I didn't know this existed until he
mentioned it. I do like the idea. Most web server software has support for
WebDav, or there are webdav add-ons. It means I don't need to run PHP (or
node.js) on the server, which significantly reduces the resources needed on
the server. So, I've been experimenting with WebDav.
I've found that it works very well once the web server is set-up properly.
*Using Lighttpd*, it works without issues. Http Basic Auth (or digest auth)
works without issues. I haven't tried, but I don't think there would be
issues using client certificate authentication if one wanted that level of
security on the network link.
*Using Apache*, it also works with basic or digest auth. One interesting
difference, Apache seams to track the last time you loaded the file (get
request) and compares that to the last file modification time-stamp. *If
the last modification is newer than when you loaded the tiddlywiki file,
you get an error and the change doesn't get saved*.
You can (easily) get around this by reloading the file (browser
reload/reread button) after you save the tiddlywiki file. It might be a bit
annoying but it does solve the issue of conflicting edits if two people are
working on it at the same time. On the down side, the 2nd person will have
to re-load the file and re-do all their work (of course browser tabs help
with that).
I don't use nginx, so I haven't tried that one.
<https://groups.google.com/d/msg/tiddlywiki/cO8lYpmAMWE/bKc6mPRZBgAJ> that
TiddlyWiki supports saving via WebDav. I didn't know this existed until he
mentioned it. I do like the idea. Most web server software has support for
WebDav, or there are webdav add-ons. It means I don't need to run PHP (or
node.js) on the server, which significantly reduces the resources needed on
the server. So, I've been experimenting with WebDav.
I've found that it works very well once the web server is set-up properly.
*Using Lighttpd*, it works without issues. Http Basic Auth (or digest auth)
works without issues. I haven't tried, but I don't think there would be
issues using client certificate authentication if one wanted that level of
security on the network link.
*Using Apache*, it also works with basic or digest auth. One interesting
difference, Apache seams to track the last time you loaded the file (get
request) and compares that to the last file modification time-stamp. *If
the last modification is newer than when you loaded the tiddlywiki file,
you get an error and the change doesn't get saved*.
You can (easily) get around this by reloading the file (browser
reload/reread button) after you save the tiddlywiki file. It might be a bit
annoying but it does solve the issue of conflicting edits if two people are
working on it at the same time. On the down side, the 2nd person will have
to re-load the file and re-do all their work (of course browser tabs help
with that).
I don't use nginx, so I haven't tried that one.
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/603ae837-720a-4f5c-a4e4-9de40d772783%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/603ae837-720a-4f5c-a4e4-9de40d772783%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.