And here is the link!

https://gist.github.com/Arlen22/bbd852f68e328165e49f

Enjoy!

On Thu, May 25, 2017 at 3:37 PM, Arlen Beiler <[email protected]> wrote:

> Here is a gist I made showing the gist of how to get multiple TiddlyWikis
> to run under one ExpressJS server. It works perfectly with Node HTTP server
> as well, but you need to do the express routing yourself.
>
> On Thu, May 25, 2017 at 1:47 PM, 'Mark S.' via TiddlyWiki <
> [email protected]> wrote:
>
>> Your separate server could also run in another instance of node.js. But
>> it would have it's own IP number and so the served files could not be
>> accessed via TW as relative files. If there's a way to make the file server
>> run in the same instance as TW with the same IP and port, that would be
>> interesting to learn about.
>>
>> Mark
>>
>> On Thursday, May 25, 2017 at 10:25:02 AM UTC-7, Conner Phillips wrote:
>>>
>>> You say a separate file server. Wouldn't just the appropriate module
>>> being loaded into the node.js server get the job done? What is the current
>>> state of media in node.js tiddlers? 64-bit encoded objects?
>>>
>>> On Thursday, May 25, 2017 at 6:27:14 PM UTC+2, Mark S. wrote:
>>>>
>>>> The ability to handle larger files is going to depend on the physical
>>>> abilities of your machine. I have a pretty good set up, but hit the wall
>>>> between around 20 megs. If you load your TW on a tablet or phone, the limit
>>>> is going to be lower. It takes about 30 seconds or more to load a 10 meg
>>>> file on my phone ... and sometimes it won't load at all. The thing to do
>>>> would be to test your system. You can load up your TW pretty quickly by
>>>> dragging and dropping images.
>>>>
>>>> With node.js, you can't refer to external images or files on your local
>>>> device. To access them, you would need a separate file server. To me that's
>>>> a big reason not to use node.js.
>>>>
>>>> Good luck!
>>>> Mark
>>>>
>>>> On Monday, June 23, 2014 at 1:29:23 PM UTC-7, Ulrik Stervbo wrote:
>>>>>
>>>>> Hello list,
>>>>>
>>>>> What are the advantages of running the tiddlywiki as a node.js app
>>>>> rather than a single file? Other than the wiki is being run as a server 
>>>>> and
>>>>> can be accessed from outside.
>>>>>
>>>>> Are there any performance advantages? I am particularly thinking about
>>>>> memory usage: are the tid-files in the node.js read as needed or are they
>>>>> all read in at start up, making it not much different from the single HTML
>>>>> file variant?
>>>>>
>>>>> I am interested, because it seems I will be generating a large file -
>>>>> for now it is just 3mb, but when I add some long tables, it may become
>>>>> close to 10mb. And I will keep adding. I have seen posts that tiddlywiki
>>>>> starts to slow down dramatically at some point (20mb if my memory serves 
>>>>> me
>>>>> well). Is there any way to avoid that?
>>>>>
>>>>> Thanks for any comments.
>>>>>
>>>>> Cheers,
>>>>> Ulrik
>>>>>
>>>> --
>> 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/a3b37a97-b045-45ae-9e29-1b5d2cf48bfb%40googlegroups.com
>> <https://groups.google.com/d/msgid/tiddlywiki/a3b37a97-b045-45ae-9e29-1b5d2cf48bfb%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/CAJ1vdSRCNANZcHmHCM-2zvVkE-SSbi%2BQgU%3D565Mr34Y9EOD5Uw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to