Ciao Arlen Its an interesting discussion.
The thing I want to underline is difference between the AIMS of different kinds of users. I do NOT find it a problem the whole thing it can potentially do IS under-documented. Why? Because I'm not trying to do anything other than use it to save. And previously we worked through many details of how to do that here in GG. Its pretty clear now how to set it up (though maybe needs bringing together & written up tighter sometime?). When I have my "get-on-with-it" hat on (I have to get something written by Thursday etc.) I'm NOT interested in anything other than being able to save TW seamlessly--which TiddlyServer(Lite) does. And special because it DOES THAT other things don't. I already had auto-backup running for years so that addition adds nothing practical for me. I think my broader question is actually about what is the MOST MINIMAL install needed to let you save TW? I.e. a VERSION as NARROW as possible for that purpose. I think your interest is about how to widen it up. Its that very liberal, truly generous widening that I feel for idiots like me might be confusing. And its around that that I find the naming confusing--many things start to blur. Best wishes Josiah On Saturday, 7 October 2017 17:01:28 UTC+2, Arlen Beiler wrote: > > Hi TiddlyTweeter, > > >> The point is this ... FUNCTIONALLY I'm a user who downloaded the >> "Bundled" (non-npm) version to be an alternative "TiddlyWiki-saver" to >> TiddlyFox. Nothing more. And I had no idea it did more than that. IF it has >> additional backup options then I'd need clearer documentation of that. I >> might use them, though I backup using normal backup software. > > > Everything I've ever said about TiddlyServer applies equally to the > "Bundled" (non-npm) version and the "Source Code" (npm ) version *after > you run "npm install" on the npm version.* > > "npm install" pulls in TiddlyWiki from NPM, whereas the bundled version > already has tiddlywiki from npm included. > > If all you use it for is saving, that's fine. The NodeJS version of > TiddlyWiki, and thus TiddlyServer, has some useful features, but they are > not yet well documented. That was the whole point of making TiddlyServer, > was to allow NodeJS TiddlyWiki data folders (there are a couple examples in > editions) to be mounted, but it combined several other things that have > been requested on this GG as well, such as the ability to serve static > files alongside the TiddlyWiki server, and of course saving single-file > TiddlyWikis. > > I am currently trying to make the configuration more user-friendly as > well. And yes, I do need better documentation :) I'm thankful for those of > you who have taken up the slack in figuring it out and helping others > figure it out, including your help @TiddlyTweeter. > > If you want more information on using the NodeJS version of TiddlyWiki, > you can check out these links, but I digress. What TiddlyServer does is > mount TiddlyWiki Folders (aka data folders) at a path so they can be > edited, just like the server command. Under the hood, it actually uses the > same code as the server command. > > - http://tiddlywiki.com/#TiddlyWiki%20on%20Node.js > - http://tiddlywiki.com/#ServerCommand > - http://tiddlywiki.com/#Installing%20TiddlyWiki%20on%20Node.js > - http://tiddlywiki.com/#TiddlyWikiFolders > > Arlen > > On Sat, Oct 7, 2017 at 8:53 AM, @TiddlyTweeter <[email protected] > <javascript:>> wrote: > >> Ciao Arlen >> >> I probably don't understand my own question :-). >> >> The point is this ... FUNCTIONALLY I'm a user who downloaded the >> "Bundled" (non-npm) version to be an alternative "TiddlyWiki-saver" to >> TiddlyFox. Nothing more. And I had no idea it did more than that. IF it has >> additional backup options then I'd need clearer documentation of that. I >> might use them, though I backup using normal backup software. >> >> I think the difficulty I am pointing at is neither directly mine nor >> yours. Its in-between. Your coming from a great deal of knowledge and daily >> practice. I'm coming from a place of only wanting to be able to seamlessly >> save my TW. >> >> Seamless saving by ONE product with ONE name that does ONE thing I think >> is what makes it SO important right now. IF its also got other useful >> features then that is good too BUT at a certain point when a newbie starts >> hitting code you have to enter through the console it starts looking less >> simple and gets confusing. >> >> In other words: Have a dumb-version where you need know nothing else than >> how to install it (which is not so easy for dumb people already :-) that is >> targetted wholly at saving (only)? >> >> Let's keep talking till both of use are clear what the other means, okay? >> >> Best wishes >> Josiah >> >> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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/4827dc02-531e-44fa-9f10-bf3a346de96b%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tiddlywiki/4827dc02-531e-44fa-9f10-bf3a346de96b%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> 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 [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/294da9a8-3f73-44d0-b814-2cf7835ebea6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
