Hi, I had take a look FenixWebServer and found that it basically just a simple http server with a great setting UI based on nw.js.
Because TW5 only use "PUT" method to upload full wiki file, it isn't hard to add support to FenixWebServer (add handler
here) or any kind of http server.
But what's your main purpose to select FenixWebServer to make a fork? The great setting UI? Or just easy to use (setup path, port, account, and then start)?
For "easy to use", a simplest Tiddlyserver which run a WebDAV server and serve TW5 html file will also do that.
There are so many different WebDAV server implement you could try, eg:
this and
this.
But this use case (WebDAV) had several issues:
1. any update will upload a full wiki file, a least 2MB for a empty wiki (v5.1.17), that's not small for a mobile user.
2. In most implement, if you set authenticate, then everyone must login to view and with edit permission, you can't let guest view without edit permission.
3. the wiki only load once when open, if there are multiple user edit and save, one of their data will be lost.
To overcome those issues, I make a
fork of widdly, merge the benefit of PutSaver (WebDAV) and TiddlyWeb plugin, detail can see
here.
Although I'm still coding for more and more features, it's easy to setup and use, with more features. You can give it a try. :)
David Masterson於 2018年9月23日星期日 UTC+8上午1時41分38秒寫道: