Normally I store the data directory inside the tiddlywiki folder, but you can store it anywhere you want.
On Jan 4, 2017 12:04 AM, "Arlen Beiler" <[email protected]> wrote: > Welcome to the world of NodeJS. You can search for "commands" on > TiddlyWiki.com. That will give you all the command line options. > > node.exe tiddlywiki.js [data directory] [command [options]] > > On Jan 4, 2017 12:00 AM, "Arlen Beiler" <[email protected]> wrote: > >> If you do not specify a directory as the first argument after >> tiddlywiki.js, it will use the current directory. Most of the commands use >> that directory. So I recommend you set one. >> >> On Jan 3, 2017 11:56 PM, "Arlen Beiler" <[email protected]> wrote: >> >>> If you specify --init or --load instead --server, then tiddlywiki.js >>> will make that the data directory. Then you specify that directory when you >>> specify --server and it will serve the files from that folder. >>> >>> You can find more info on TiddlyWiki.com or by exploring the code. >>> >>> On Jan 3, 2017 10:55 PM, "'Mark S.' via TiddlyWiki" < >>> [email protected]> wrote: >>> >>>> In your example, what is "../data/wiki1" and where does it come from? >>>> >>>> Thanks! >>>> Mark >>>> >>>> On Tuesday, January 3, 2017 at 7:26:43 PM UTC-8, Arlen Beiler wrote: >>>>> >>>>> Anything is possible over HTTP. How are you going to save changes? >>>>> >>>>> From reading your email, I guess you don't know that you can just >>>>> download any tag or the master from the TiddlyWiki GitHub repository, drop >>>>> node.exe into it and call "node.exe tiddlywiki.js ../data/wiki1 --server" >>>>> and your good to go. Easy on Windows, don't know about Linux or Mac, but >>>>> you're a software developer :) >>>>> >>>>> (At first I was going to use the stock "I guess you know...") :-) >>>>> >>>>> Also several of us are working on serving multiple wikis as separate >>>>> folders instead of seperate server instances. >>>>> >>>>> https://gist.github.com/Arlen22/bbd852f68e328165e49f >>>>> >>>>> Hope that helps. >>>>> >>>>> On Jan 3, 2017 7:50 PM, "Evade Flow" <[email protected]> wrote: >>>>> >>>>>> > is there some way I can access/modify this collection of files >>>>>> using only git and a browser? >>>>>> >>>>>> Driving home this evening, I realized this was a bit of a silly >>>>>> question for somebody who professes to be a software developer by trade >>>>>> to >>>>>> ask—doh! (Can you tell I'm not a web developer?) Looking at the files >>>>>> processed by tiddlywiki+NodeJS, I see that *none* of them are HTML. >>>>>> It truly is "tiddlers all the way down", so... *something* has to >>>>>> convert all those .tid files to HTML so the browser can display them. >>>>>> >>>>>> I guess I should rephrase my question as: is there some way of >>>>>> serving multi-file TW content that requires less setup work than NodeJS? >>>>>> I'm thinking about how Python contains builtin modules that let you run >>>>>> something like this in a folder: >>>>>> >>>>>> $ python -m SimpleHTTPServer 8000 >>>>>> >>>>>> >>>>>> For me, this would be a big win because (as it happens) just about >>>>>> every machine I work on already has Python installed. And they *all* >>>>>> have Perl, which I believe has a similar (built-in) capability[?] So it >>>>>> would be "one less thing" to worry about it when configuring a new >>>>>> environment. >>>>>> >>>>>> >>>>>> On Tuesday, January 3, 2017 at 4:44:43 PM UTC-5, Evade Flow wrote: >>>>>>> >>>>>>> I've been experimenting with TiddlyWiki and NodeJS, and discovered >>>>>>> that 'importing' my mono-html file (using tiddlywiki --load) causes >>>>>>> it to be converted into a bunch of discrete files. Further experiments >>>>>>> reveal that it is possible—seemingly, at least—to sync these files (and >>>>>>> hence, my entire wiki) to multiple machines using git push/pull. >>>>>>> The one catch is: it appears that the only way to actually *use* a >>>>>>> TiddlyWiki structured this way is to serve it using NodeJS? Is that >>>>>>> correct? Or... is there some way I can access/modify this collection of >>>>>>> files using only git and a browser? >>>>>>> >>>>>>> I ask because the setup I'm fumbling my way towards seems a bit... >>>>>>> cumbersome. I'm a software developer by trade, so sync'ing git repos to >>>>>>> multiple machines comes as naturally as breathing. In contrast, doing a >>>>>>> local install of Node + npm + tiddlywiki on each machine I want to >>>>>>> access >>>>>>> the data from feels like a lot of extra effort. I use Windows and Linux >>>>>>> at >>>>>>> work, and OS X at home, and I'd rather not bother figuring out the >>>>>>> nuances >>>>>>> of how to do that dance on all three platforms—especially given that I >>>>>>> don't have admin/root access on all the machines I'd like to access my >>>>>>> wiki(s) from. >>>>>>> >>>>>>> I already have a *killer* setup for managing my myriad config files >>>>>>> (.vimrc, .zshrc, .tmux.conf, etc.) and various plugins using myrepos >>>>>>> <https://myrepos.branchable.com/> and vcsh >>>>>>> <https://github.com/RichiH/vcsh>. *Everything* is stored in git, so >>>>>>> I can sync my setup around to whatever machines I want. It would be >>>>>>> enormously helpful if I could do the same with my TiddlyWiki(s). Is this >>>>>>> possible? >>>>>>> >>>>>>> *NOTE*: After trying it a few times, I don't have much interest in >>>>>>> trying to sync changes to monolithic TW files. The mono-HTML files are >>>>>>> huge, and the diffs contain so much 'noise' that trying to merge updates >>>>>>> from multiple machines seems like an impossibility. (Perhaps I'll find >>>>>>> that >>>>>>> the multi-file layout has quirks/pitfalls of its own, but so far, it >>>>>>> seems >>>>>>> really easy to understand and reason about...) >>>>>>> >>>>>> -- >>>>>> 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/e5c24183-b6aa-4 >>>>>> 3a1-a682-2fc8137f4fab%40googlegroups.com >>>>>> <https://groups.google.com/d/msgid/tiddlywiki/e5c24183-b6aa-43a1-a682-2fc8137f4fab%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/ms >>>> gid/tiddlywiki/3a14ab02-3b7a-43c0-8716-f0e466d8a4dd%40googlegroups.com >>>> <https://groups.google.com/d/msgid/tiddlywiki/3a14ab02-3b7a-43c0-8716-f0e466d8a4dd%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/CAJ1vdSTjn9FFJV6RAm9zbJLVjxsabDJrzuT1R71Sk5myrG%2BZdA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
