> If I only need the tiddlywiki.js file and node.exe that trims things down
considerably.
Ah. I see now that I misunderstood. You didn't say that having *only *
tiddlywiki.js and node.exe was sufficient, you said to clone the TW repo
and drop node.exe into it. Instead, I tried copying both node.exe and
tiddlywiki.js into *my *TW folder, and got:
module.js:472
throw err;
^
Error: Cannot find module './boot/boot.js'
at Function.Module._resolveFilename (module.js:470:15)
at Function.Module._load (module.js:418:25)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (C:\Users\wod2fh\projects\reverie\tiddlywiki.js:7:
11)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
Now I'm thinking perhaps I'll try using git submodules to make the TW repo
a 'sub-repo' of my tiddler repo...
On Wednesday, January 4, 2017 at 11:31:09 AM UTC-5, Evade Flow wrote:
>
> > 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"...
>
> That's actually *really* helpful, thanks. You mean: I don't need to
> download *all* of node/npm? I found these instructions
> <https://gist.github.com/massahud/321a52f153e5d8f571be> for installing on
> Windows, and (more-or-less) followed them, installing the npm + nodejs zip
> package from here <https://nodejs.org/dist/v7.2.1/>, as recommended in
> one of the comments in the gist. It wasn't difficult, but I was a bit
> surprised when I saw that the node-v7.2.1-win-x64 folder takes up 70 MB.
> I mostly do embedded systems development, so I sometimes have these "Get
> off my lawn!" moments when something dumps a ton of files onto my system
> whose purpose I don't really understand. (This, even though I've got 315 GB
> free on that hard drive. I don't claim it makes any sense. `:-] )
>
> Now that I look at it, I see that the node_modules/tiddlywiki subfolder
> itself is responsible for ~27 of those 70 MB. And the editions folder
> (which I assume I don't need?) contains some 13 MB of 'stuff'. If I only
> need the tiddlywiki.js file and node.exe that trims things down
> considerably. I'll give it a try!
>
>
> On Tuesday, January 3, 2017 at 10:26:43 PM UTC-5, 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-43a1-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/msgid/tiddlywiki/3ea255d4-8604-4b8f-99d6-39d379c8f98a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
