On Monday, May 28, 2018 at 3:25:43 PM UTC-4, Mat wrote: > > Lost Admin - thank you for your information! Some questions: > > *WebDAV* >> >> *...* >> > *OS* : Any (Apache) or windows (IIS) >> > > What does this mean - what's the difference? > I'm limiting the SetUp matrix to include set-ups custom made for TW - OR - > instructions(!) on how to adapt some other "system" to TW. When it comes to > WebDAV, I see @PMario has kindly made instructions for IIS > <https://tiddlywiki.com/#Saving%20via%20WebDAV>. From that tiddler I > don't understand if there are other options for someone who is not very > tech savvy. is there? >
The Apache HTTPD server can be installed on pretty much any OS (it is available on most UNIX and UNIX like OSes, including Linux) but also available for OSX (Apple) and Windows. I'm working on instructions for setting it up on FreeBSD (UNIX-like), Debian Linux, and Windows. I already made basic setup instructions on this forum (now buried and probably lost). @PMario made his instructions, which I followed to set-up IIS. So really you can run a webdav server on pretty much any OS with the Apache HTTPD server and on windows specifically you can also run webdav with IIS. To make this even more complicated, there is an entire webdav server written in PHP (called sabre/dav). I haven't tested this but it is pretty popular. PHP runs on pretty much any OS, so it should work pretty much any OS. PHP is an interpreted language (like Python or Perl) and needs server software that supports it. Since Apache (and Nginx, and IIS) support PHP, you can pretty much run Sabre/dav on anything. If you are only going with "that we have instructions for", you still have a bit of a dilema as there is absolutely nothing special about the setup of WebDAV for Tiddlywiki (you just need a properly set-up WebDAV server). So instructions (not unique to TiddlyWiki) are out there. But if you want specific to TiddlyWiki anyway, then IIS for now (and Apache if you can find my old instructions or wait until I finish the new ones with better screenshots). Web servers are complicated. There will probably never be instructions for the "not very tech savvy". But there will (hopefully) be step-by-step instructions for the brave and soon-to-be-tech-savvy. > > >> *Portable* : No (or maybe with Apache portableapps) >> > > To qualify as portable it should exist as a self-contained solution by > itself. > > (Should I change the category "portable" to instead be "self-contained"?) > Honestly, I think this is always going to be debatable. The intent you have is subtle and simple terms are going to have broader meaning to different people. > > > *PHP (store.php)* >> > > I've renamed the set-up to now be as you phrase it here, yes? > > *Dependencies* : Web server & PHP (confirmed on Apache 2.4 with php 5.6) >> > > I have classed "PHP", or "PHP (store.php), as a server... but "a server" > is rather the requirement for this (right?). > Yes, that works. > > > *NoteSelf* >> >> *format* : json >> > > Hm, that woudl be the "code-format", for tiddlers right, not NoteSelf per > se? By "format" I tried to find a label for: > > How is the set-up solution manifested? >> What format is this piece of software in? This >> might affect how complicated it is to install/set it up. >> *Option values, predefined* >> - html-file >> - .tid-files >> - TW-plugin >> - Browsr_add-on >> - Browser-in-itself >> - App > > > I would guess NoteSelf is an "App" in this sense, i.e a separate software. > Would you say my lable "format" is poorly chosen? Any better suggestion? > Looking at my list above, I'm wondering if ".tid-files" really is > relevant? > > ...and maybe I *should *include json, i.e use file-format of tiddlers as > a criteria? This may be important if one wants some kind of API > integration, right? > I'm not 100% sure how you want to express this. NoteSelf is a touch more complicated than TiddlyWiki in in it's most basic form and yet is also (at it's core) only a couple of plug-ins to TiddlyWiki. So ... format, the log explanation: NoteSelf the very first time you load it, is an HTML file. It is TiddlyWiki with some plugins. One of those plugins takes each Tiddler and converts it to JSON (an in-memory data structure) and stores it in browser storage. The format of the browser storage varries depending on the browser used but is basically still JSON. This is PouchDB So, in the above sense you now have a multi-file stand-alone tiddlywiki. One file is HTML, the other is in whatever format your browser uses for local storage. Firefox, for example, uses sqlite files as the on-disk format (but each tiddler is saved as json within sqlite records). Now, things get really confusing. We add in CouchDB. The plug-ins that make NoteSelf include support to sync what is in browser storage to a database server (specifically one running CouchDB). Internally CouchDB uses the JSON data structure and so when it saves, it is also JSON. Each tiddler is a single JSON structure inside a larger JSON structure. So, your multi-file wiki consists of one HTML file and one or more JSON data structures stored in files managed by two other programs (your browser and the CouchDB server). However, the HTML file is pretty much static. Your changes always store to PouchDB and then sync to CouchDB. Perhaps in the spirit of "keep it simple", the "format" should be N/A or proprietary as only technically savvy people will be able to dig the data out of the raw on-disk files of CouchDB or the web browser. I may have been getting to specific for you. I didn't know you have a small pre-defined set. > > <:-) > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/bbdd271b-15a7-4d47-b136-22a9fdca82c4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
