Re: [tw5] If I wanted to start a discussion ...

2022-12-10 Thread Arlen Beiler
>From my linux experience, the sweet spot is having everything required to
immediately get down to business in every single situation.

At minimum, having apt, nano, curl, and ssh installed is pretty much a no
brainer. But you don't need the dev tools, you don't need the docker
runtime or VMs, you don't need a graphical environment (many choices, none
perfect), but you do need the basic bash scripting tools.

My current philosophy for Tiddlywiki is "if you can do it with a plugin, do
it". Core doesn't really need more user comforts but extensibility is an
ever expanding work in progress. There are certain features that I always
add to every single wiki, like certain macros that I find useful, and if
you find yourself always doing that, that can indicate it's a feature that
could be useful in core. Macros and small style tweaks are especially good
candidates for that. Also, if you're good at coloring a UI, palettes
need more diversity. If someone makes a really good theme that answers ALL
the scenarios perfectly, that would be a candidate for an official plugin.

This is something that I've related to a lot in working with TiddlyWiki. I
made TiddlyServer, for instance, (https://arlen22.github.io/tiddlyserver/),
and I made it entirely based on code that was already existing in TW5,
mostly just using standard features in boot and core. The core is
intentionally built to be extended, and it was the core code that actually
gave me the idea for how to write TiddlyServer. I didn't come up with it, I
just saw the pattern and used it.

That being said, the thing I have made more pull requests for than anything
else is the boot folder loading code. After four or five different PRs
trying different ways of approaching the situation, I finally came up with
the rather simple solution of dividing the startup function out into three
separate functions which would allow the init and exec portions to remain
the same while being able to change the load portion to use async calls.
That PR was accepted and I can now happily override the data loading with
any async adapter I want without worrying about maintaining the init and
exec portions every time they change. The main use case for this would be
"TW5 in the cloud" and other "NodeJS TiddlyWiki5" scenarios where blocking
is undesirable or impossible.

https://github.com/Jermolene/TiddlyWiki5/blob/master/boot/boot.js#L2491-L2497

$tw.boot.startup = function(options) {
options = options || {}; // Get the URL hash and check for safe mode $tw.
boot.initStartup(options); $tw.boot.loadStartup(options); $tw.boot.
execStartup(options); };


So my two cents is: do what you can as a plugin, and think of the most
generic and useful ways to make improvements to core that retain existing
compatibility and keep things organized and performant.


On Fri, Dec 9, 2022 at 7:17 PM Charlie Veniot  wrote:

> *I'd probably do something like this:*
>
> What is the sweet spot of how much should be core TiddlyWiki and how much
> should be plugin?
>
> If there were no plugins needed because everything anybody would ever need
> would be in the core.  Would it make core TiddlyWiki too heavy?
>
> And if we were to make TiddlyWiki as light as possible, and make
> everything a plugin, would that be too unwieldy?
>
> Is there such a thing as one sweet spot, or would it make more sense to
> have a handful of sweet spots available?
>
> To have a handful of sweet spots, they should be easy to create and
> maintain.  Probably makes sense to have a slimmest bare bones TiddlyWiki
> core, with "big plugins" to easily create each alternative "sweet spot".
>
> What do you think?
>
> *If I wanted to get into that kind of discussion, I think that's how I'd
> kick things off.*
>
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/6a09dac3-39f6-4356-922d-3f08ba02b0b2n%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSS3V%2BmbucwAMRG%2BC21QDnVvZDMcQKascKEu2W69EFMadg%40mail.gmail.com.


[tw5] TiddlyServer updated to TiddlyWiki 5.2.1

2022-03-20 Thread Arlen Beiler
Hi everyone,
Sorry for the long silence.
I've updated TiddlyServer to point to TiddlyWiki 5.2.1 (using my production
builds of course). In the future I'll try to get these updated quicker. The
process is pretty streamlined for me at this point.
Enjoy
Arlen

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTOHr%2BOU_Z_wRTBBY8_o_Bhtin%3Dem-Bvx6GutqmLpXN7Q%40mail.gmail.com.


Re: [tw5] Announcing TiddlyMarker v0.1.0-alpha for Firefox

2022-03-20 Thread Arlen Beiler
To use this with TiddlyServer you just need to make sure you are making all
requests relative to the tiddlywiki you are targeting. TiddlyServer loads
NodeJS instances dynamically as they are requested. So most likely you are
making the call to the root path ("http://localhost/;) and usually that is
not where the tiddlywiki is mounted. Instead you need to change those calls
to the path "http://localhost/personal/notes/; or whatever the path to your
wiki is. That's just my guess without really taking a look at it or trying
anything out. I just saw you said you were using the TW webserver api.

On Wed, Jun 3, 2020 at 2:40 AM Yestin Harrison 
wrote:

> I've been working on a browser extension to suit a particular manner of
> bookmarking with TiddlyWiki, unimaginatively titled TiddlyMarker. The basic
> idea is a simple button that produces a bookmark tiddler from the current
> tab, with various ways of getting that tiddler into a wiki, and flexibility
> as to its structure. Currently, the two modes of saving work via the TW
> webserver API, and simple browser downloads, respectively.
>
> Anyone who wants to give it a try can clone the repository at
> https://git.ylh.io/tiddlymarker and follow the README to get up and
> running.
>
> Of interest to developers: the code is a bit of a mess (JS isn't really my
> forte), and it's missing the planned saving mode for adding to an already
> open TiddlyWiki tab; getting the extension to play nice with $tw in the
> page context is proving to be a bit of a faff, especially in a way that can
> easily be ported to Chrome (that's planned too). Commented sections show
> the beginnings of such a mode, and patches are welcome; email them to
> yes...@ylh.io.
>
> It's in a reasonable working state, and I'm now soliciting feedback before
> I port it to Chrome and package it for Mozilla and Google.
> Enjoy!
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/6c601e92-9508-4b4a-9b75-2b6d2f21d68f%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTtBHcUpzvWYMt1DzRv_paSP1Kfz9xjKsX1U5M2MpEoew%40mail.gmail.com.


[tw5] Interesting test for unique string processing

2020-12-29 Thread Arlen Beiler
Here is an interesting test to see which method of unique strings is faster
in Javascript. Paste it into your browser console in a new tab and see
what happens.

for (let r = 0; r < 100; r++) {
let test = Math.random().toExponential(10);
let count = 1000;
let test1 = {};
let test2 = [];
console.time("test 1");
for (let i = 0; i < count; i++) {
let item = test + "" + i;
if (!test1[item]) test1[item] = true;
}
console.timeEnd("test 1");
console.time("test 2");
for (let i = 0; i < count; i++) {
let item = test + "" + i;
if (test2.indexOf(item) === -1) test2.push(item);
}
console.timeEnd("test 2");
}

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQqnSJG8iZhd-QizDA%3D2OMXq5ecAi3jLLVuY-5yQDLsTQ%40mail.gmail.com.


Re: [tw5] TiddlyServer and SSL

2020-09-05 Thread Arlen Beiler
Set the https property to a Javascript file which exports a function named
serverOptions. It is called for each listener instance started with one
argument and is expected to return the HTTPS options object for HTTPS
createServer

exports.serverOptions = function(address) { return { key: ..., cert: ... };
}


https://nodejs.org/dist/latest-v12.x/docs/api/https.html#https_https_createserver_options_requestlistener


On Fri, Sep 4, 2020 at 7:26 PM Calvino  wrote:

> Hi,
> Can anyone provide a document about how to bind Arlen's TiddlyServer with
> SSL cert files? I already have them for TiddlyWiki and it works okay ... I
> want to run TiddlyServer and use the same ones, but not sure how to
> reference them in the config file.
>
> If possible I'd rather do that then try to figure out an SSL reverse
> proxy, which I've run into a little trouble with on Windows.
>
> Thanks!
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/5c5a796a-0b67-4f27-b70a-6b028ff6d1e1n%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTLTU7%2BsX%2BbuEanm9S3GTkNyLB_F8%3DCF7A5DbY4YA6cqw%40mail.gmail.com.


Re: [tw5] Running JS REPL inside TW

2020-05-23 Thread Arlen Beiler
I would say if you want to write it yourself, that's probably your best
bet. For TiddlyWiki we just use the browser console, and TiddlyWiki doesn't
focus on Javascript as a user feature so this isn't a core focus.

I would say use a widget. If you look through the /core/modules/widgets/
folder you should find one that's close. The text widget comes to mind as a
good example that I recently used. That will show you how to insert a DOM
node at that place in the document which can then be operated on however
you want. If you use the text widget, just replace the text node with a div
element or something like that. It's pretty simple. You can also use the
set widget to pass in variables or simply refer to any tiddlers you want
using "this.wiki" I believe.

On Fri, May 15, 2020 at 5:16 PM Scott Sauyet  wrote:

> My recent success dynamically building a stand-alone TW to document a
> corporate system -- with many thanks due to helpful people here! -- has
> made me want to revisit something
>  I
> stopped working on several years ago when I changed jobs.  It's another bit
> of documenting a system (this time a code library)  by dynamically
> generating a TW.  I have most of the pieces in place given what I've done
> recently.  (It's behind a corporate wall, I'm afraid, so I can't share, but
> it's working quite well.)
>
> But there is one piece that I haven't even considered yet.  If you visit
> the Ramda documentation , you will see in the
> top-right of the code examples the choice of visiting that example in Ramda's
> REPL  or to open it inline.  For the inline
> part we're embedding  RunKit
> .  This is a nice feature for library
> documentation.  Sanctuary.js  has something
> even nicer.
>
> I have no problem trying to write my own version of something like this as
> a TW plugin, but I was wondering if this has already been done.  Searches
> for REPL and Tiddlywiki turned up nothing useful.
>
> Are there any code sandbox / REPL plugins already available?  Or is there
> anything similar that I might look to for inspiration, some way to sandbox
> some dynamic JS code away from the TW environment?
>
> Cheers,
>
>   -- Scott
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/101de743-eab4-45c7-a251-2ed782815e59%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTJhB662-U%2BuoFMOJ3buXuhpMQ%2BkFhEhO4TxXTqQSBVNQ%40mail.gmail.com.


Re: [tw5] Re: More redesigning TW. GettingStarted should be revamped.

2020-05-22 Thread Arlen Beiler
I understand the point. I'm not sure that a favorite star would be the most
obvious way to do this. I think rather the getting started page should
define a few terms (3 terms) that people have trouble with. It could also
just present the default tiddlers edit box and explain what it does and
where to find it (home page of the control panel). Default isn't a bad name
for it once you know what it does.

On Fri, May 22, 2020, 07:45 Paco Rivière  wrote:

> El divendres, 22 maig de 2020 13:29:40 UTC+2, TiddlyTweeter va escriure:
>>
>> My apologies. I thought it more.
>>
>> You might want to retry using your specific need as the title!
>>
>> TT
>>
>
> Sorry. I don't get you? Abt, redesign: Getting started should be revamped.
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/0416d02c-9c44-42bd-a6e3-55408f5477de%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTKLStBKtM1yi1xbLYwB8h%3Dk-dNOJVPkFy2eFsmwPB-BA%40mail.gmail.com.


Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-05-21 Thread Arlen Beiler
What is the terminal (command line) output? If you can copy in the full
logs (minus the names if it matters) that would be great. Also, is the
checkmark red or grey? And can you verify that your wiki is at least 5.1.15?

On Thu, May 21, 2020 at 10:24 PM Morgaine O'Herne 
wrote:

> Yes, and that's exactly what it isn't doing. When I refresh the page, the
> changes are gone. It is not saving.
>
> On Thu, May 21, 2020, 5:43 AM Arlen Beiler  wrote:
>
>> I'm sorry, I'm not completely following. If you open an empty single file
>> wiki, clicking the check mark will download a copy of the wiki at that
>> moment. but autosave is turned on by default so it should already be saving
>> the file back to its original location.
>>
>> On Wed, May 20, 2020, 23:28 Morgaine O'Herne 
>> wrote:
>>
>>> Arlen and Matt, thank you for the time and labor you've put into this.
>>> When I go to the link in my browser there is an empty wiki, but when I
>>> edit it and save it, it downloads a saved copy to my Downloads folder, but
>>> does not save the original.
>>> Any help is greatly appreciated.
>>>
>>> Morgaine O'Herne
>>>
>>> On Friday, April 24, 2020 at 2:39:44 PM UTC-6, Arlen Beiler wrote:
>>>>
>>>> Hello Everyone,
>>>>
>>>> I've upgraded TiddlyServer to target 5.1.22.
>>>>
>>>> @someguynamedmatt helped rearrange the build process, resulting in a
>>>> clean production build. So, I've now published TiddlyServer to npm and you
>>>> can install it by running
>>>>
>>>>  npm install -g tiddlyserver
>>>>
>>>> This will install it globally, which also puts it in your PATH, so you
>>>> can run it directly using
>>>>
>>>>  tiddlyserver --config /path/to/settings.json
>>>>
>>>> Windows should also work just fine. You can use the tilde (~) if your
>>>> shell supports it. I forgot to include tilde support for the config
>>>> parameter (if the shell passes it through). I'll add that in the future.
>>>>
>>>> If you don't have npm installed or you want to do a portable install,
>>>> you'll find the archives listed at
>>>> https://github.com/Arlen22/TiddlyServer/releases/tag/v2.2.0-alpha-3. I
>>>> downloaded the tgz files from npm, and the zip files are the same archive
>>>> converted to a zip file.
>>>>
>>>> I've separated out the tiddlywiki bundle into a separate npm package.
>>>> If you're familiar with that it's still the same idea. I will add more info
>>>> to the readme, but for now it's ready to use. It also includes the
>>>> client-side .js files for adding in an html page, which probably nobody
>>>> uses yet. I'm still working on the use cases and so forth for that, so
>>>> that's just a little teaser.
>>>>
>>>> https://www.npmjs.com/package/tiddlywiki-production
>>>>
>>>> As always, remember to create backups before upgrading.
>>>>
>>>> Enjoy,
>>>> Arlen
>>>>
>>> --
>>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/50e75052-985f-44a8-a5a6-a638b1fef40f%40googlegroups.com
>>> <https://groups.google.com/d/msgid/tiddlywiki/50e75052-985f-44a8-a5a6-a638b1fef40f%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/tiddlywiki/mF_3uxbth0g/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> tiddlywiki+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSR1m%3DXfqCv_MX%2BHXPUTPs8xsEPeWmRbNr7MMqqn3Z-Hkg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSR1m%3DXfqCv_MX%2BHXPUTPs8xsEPeWmRbNr7MMqqn3Z-Hkg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/CABVjSOF3SLf2tKsqnTHQQNC3_BUqWPSJBBBTdYAgR-nkp-oLgg%40mail.gmail.com
> <https://groups.google.com/d/msgid/tiddlywiki/CABVjSOF3SLf2tKsqnTHQQNC3_BUqWPSJBBBTdYAgR-nkp-oLgg%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSThXxfp7d7wfRJCCCMy3oWMSSrSHySwnvoC1xkcKqOhzA%40mail.gmail.com.


Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-05-21 Thread Arlen Beiler
I'm sorry, I'm not completely following. If you open an empty single file
wiki, clicking the check mark will download a copy of the wiki at that
moment. but autosave is turned on by default so it should already be saving
the file back to its original location.

On Wed, May 20, 2020, 23:28 Morgaine O'Herne 
wrote:

> Arlen and Matt, thank you for the time and labor you've put into this.
> When I go to the link in my browser there is an empty wiki, but when I
> edit it and save it, it downloads a saved copy to my Downloads folder, but
> does not save the original.
> Any help is greatly appreciated.
>
> Morgaine O'Herne
>
> On Friday, April 24, 2020 at 2:39:44 PM UTC-6, Arlen Beiler wrote:
>>
>> Hello Everyone,
>>
>> I've upgraded TiddlyServer to target 5.1.22.
>>
>> @someguynamedmatt helped rearrange the build process, resulting in a
>> clean production build. So, I've now published TiddlyServer to npm and you
>> can install it by running
>>
>>  npm install -g tiddlyserver
>>
>> This will install it globally, which also puts it in your PATH, so you
>> can run it directly using
>>
>>  tiddlyserver --config /path/to/settings.json
>>
>> Windows should also work just fine. You can use the tilde (~) if your
>> shell supports it. I forgot to include tilde support for the config
>> parameter (if the shell passes it through). I'll add that in the future.
>>
>> If you don't have npm installed or you want to do a portable install,
>> you'll find the archives listed at
>> https://github.com/Arlen22/TiddlyServer/releases/tag/v2.2.0-alpha-3. I
>> downloaded the tgz files from npm, and the zip files are the same archive
>> converted to a zip file.
>>
>> I've separated out the tiddlywiki bundle into a separate npm package. If
>> you're familiar with that it's still the same idea. I will add more info to
>> the readme, but for now it's ready to use. It also includes the client-side
>> .js files for adding in an html page, which probably nobody uses yet. I'm
>> still working on the use cases and so forth for that, so that's just a
>> little teaser.
>>
>> https://www.npmjs.com/package/tiddlywiki-production
>>
>> As always, remember to create backups before upgrading.
>>
>> Enjoy,
>> Arlen
>>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/50e75052-985f-44a8-a5a6-a638b1fef40f%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/50e75052-985f-44a8-a5a6-a638b1fef40f%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSR1m%3DXfqCv_MX%2BHXPUTPs8xsEPeWmRbNr7MMqqn3Z-Hkg%40mail.gmail.com.


Re: [tw5] Alternative solution of BobEXE on iPad?

2020-05-15 Thread Arlen Beiler
Actually, though, Bob uses a lighter format that does not load a full wiki
server, so if you're looking for something equivalent to Bob, that's going
to be easier for someone to come up with than trying to run the full NodeJS
server.

On Fri, May 15, 2020 at 9:33 AM Arlen Beiler  wrote:

> Basically you need an app that can run NodeJS, and although Bob isn't
> currently setup for that format, it probably could be. I'm not sure what
> would be required, nor do I know whether iOS would allow it to run in the
> background. There are ways to let it run in the background, but they're
> definitely hacks.
>
> On Fri, May 15, 2020 at 4:10 AM Angel Wong  wrote:
>
>> Hi. I would like to ask if there is any way to achieve saving tiddlers as
>> individual files on iPad since I am using BobEXE on my Windows computers
>> and tiddlers are synced with Google Drive.
>>
>> Currently, I plan to use remote desktop to control my laptop when needed
>> but it doesn't work when there is no Internet connection.
>>
>> Thank you.
>>
>> --
>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/3bf9b342-adc0-4699-8a53-143199759854%40googlegroups.com
>> <https://groups.google.com/d/msgid/tiddlywiki/3bf9b342-adc0-4699-8a53-143199759854%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTYqyPCZHBn9t0TDKo%2BdBysoaBp5mkXt_ObARK5_ZxS9w%40mail.gmail.com.


Re: [tw5] Alternative solution of BobEXE on iPad?

2020-05-15 Thread Arlen Beiler
Basically you need an app that can run NodeJS, and although Bob isn't
currently setup for that format, it probably could be. I'm not sure what
would be required, nor do I know whether iOS would allow it to run in the
background. There are ways to let it run in the background, but they're
definitely hacks.

On Fri, May 15, 2020 at 4:10 AM Angel Wong  wrote:

> Hi. I would like to ask if there is any way to achieve saving tiddlers as
> individual files on iPad since I am using BobEXE on my Windows computers
> and tiddlers are synced with Google Drive.
>
> Currently, I plan to use remote desktop to control my laptop when needed
> but it doesn't work when there is no Internet connection.
>
> Thank you.
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/3bf9b342-adc0-4699-8a53-143199759854%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSRn3HX9Uqhqk12W42O31yi4YPEUJjWp9Uwz8yhAT847CQ%40mail.gmail.com.


Re: [tw5] Re: node.js error message - ?

2020-05-12 Thread Arlen Beiler
And I mean the literal text "undefined".

Also, its tiddler type should be "application/json" if it isn't an actual
JSON file. I forget off-hand how JSON files are handled exactly, but this
one is being parsed as a JSON tiddler.

On Tue, May 12, 2020 at 7:49 PM Arlen Beiler  wrote:

> It looks like there is a JSON file with the text undefined, which is valid
> JSON.stringify output, but not valid JSON.parse input. It might be a JSON
> file or a .tid file, I'm not sure which. I'm also not sure if it's a
> regular file in the tiddlers folder or if it's in some other multids file
> or something like that, but it does look like it's in a data folder, and
> not part of a plugin or anything like that.
>
> On Tue, May 12, 2020 at 5:05 PM David Gifford  wrote:
>
>> Not sure what happened, but I basically redid the work, since it wasn't
>> much, and it "took" this time. Thanks Mark!
>>
>> On Tuesday, May 12, 2020 at 1:44:05 PM UTC-5, Mark S. wrote:
>>>
>>> Hmm, how did you import them?
>>>
>>> On Tuesday, May 12, 2020 at 11:19:32 AM UTC-7, David Gifford wrote:
>>>>
>>>> Well, Mark, the meta data for stylesheets and plugins I imported are
>>>> split into two tiddlers each, and one of them for each pair is a JSON.tid.
>>>> Is there a certain way one has to import tiddlers from a standalone into a
>>>> node.js document?
>>>>
>>>> On Tuesday, May 12, 2020 at 12:59:11 PM UTC-5, Mark S. wrote:
>>>>>
>>>>> Just passing time until someone knowledgeable comes along.
>>>>>
>>>>> It kind of looks like you might have broken a JSON tiddler. Did you do
>>>>> any editing in a JSON object -- data dictionary, for instance?
>>>>>
>>>>> On Tuesday, May 12, 2020 at 8:54:56 AM UTC-7, David Gifford wrote:
>>>>>>
>>>>>> Hi all
>>>>>>
>>>>>> I got this error message (see attached image) after editing on
>>>>>> node.js, and using
>>>>>>
>>>>>> tiddlywiki --rendertiddlers [!is[system]] $:/core/templates/static.
>>>>>> tiddler.html static text/plain --rendertiddler $:/core/templates/
>>>>>> static.template.css static/static.css text/plain
>>>>>>
>>>>>> to export static htmls. I can't tell what I did differently than
>>>>>> before. Any advice?
>>>>>>
>>>>>> --
>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/f4668c3e-3e77-4655-b105-479044131186%40googlegroups.com
>> <https://groups.google.com/d/msgid/tiddlywiki/f4668c3e-3e77-4655-b105-479044131186%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQA3w5T8gp36_Yc%3D9Jx4cSAHpoU_BwR8TmXAZkFJQR4SQ%40mail.gmail.com.


Re: [tw5] Re: node.js error message - ?

2020-05-12 Thread Arlen Beiler
It looks like there is a JSON file with the text undefined, which is valid
JSON.stringify output, but not valid JSON.parse input. It might be a JSON
file or a .tid file, I'm not sure which. I'm also not sure if it's a
regular file in the tiddlers folder or if it's in some other multids file
or something like that, but it does look like it's in a data folder, and
not part of a plugin or anything like that.

On Tue, May 12, 2020 at 5:05 PM David Gifford  wrote:

> Not sure what happened, but I basically redid the work, since it wasn't
> much, and it "took" this time. Thanks Mark!
>
> On Tuesday, May 12, 2020 at 1:44:05 PM UTC-5, Mark S. wrote:
>>
>> Hmm, how did you import them?
>>
>> On Tuesday, May 12, 2020 at 11:19:32 AM UTC-7, David Gifford wrote:
>>>
>>> Well, Mark, the meta data for stylesheets and plugins I imported are
>>> split into two tiddlers each, and one of them for each pair is a JSON.tid.
>>> Is there a certain way one has to import tiddlers from a standalone into a
>>> node.js document?
>>>
>>> On Tuesday, May 12, 2020 at 12:59:11 PM UTC-5, Mark S. wrote:

 Just passing time until someone knowledgeable comes along.

 It kind of looks like you might have broken a JSON tiddler. Did you do
 any editing in a JSON object -- data dictionary, for instance?

 On Tuesday, May 12, 2020 at 8:54:56 AM UTC-7, David Gifford wrote:
>
> Hi all
>
> I got this error message (see attached image) after editing on
> node.js, and using
>
> tiddlywiki --rendertiddlers [!is[system]] $:/core/templates/static.
> tiddler.html static text/plain --rendertiddler $:/core/templates/
> static.template.css static/static.css text/plain
>
> to export static htmls. I can't tell what I did differently than
> before. Any advice?
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/f4668c3e-3e77-4655-b105-479044131186%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQdG9sMzev1vFC4ajJCWAUHBLz94TkEXAH98KA0Pr54aA%40mail.gmail.com.


Re: [tw5] what's the right way to install plugin(which has dependency) on TW5+node.js?

2020-05-12 Thread Arlen Beiler
You did it correctly. Dependencies are not installed automatically in this
case. Why? Probably for security reasons. So you don't update a plugin and
suddenly get a new dependency installed. Jeremy has been quite conscious of
this over the years.

On Sun, May 10, 2020 at 8:24 PM yrosgi L  wrote:

> I followed the guide and edited tiddlywiki.info by adding "zh-CN" into
> language section, then restart the server and change the language but
> nothing works. By reading the plugin.info I found that it has a depends
> on "zh-Hans". So, after adding this depends into tiddlywiki.info, both
> the "zh-CN" and "zh-Hans" are worked well.
>
> My question is: Why the dependents do not install automatically, or is
> that mean the way I install plugin was wrong?
>
> Thanks.
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/25e93b59-d851-46df-9dca-14f5dd7d0ac6%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSNecY5WoCQLzu4c5knCO1WSr0Ov7Wgd7tVSZE-jSE_Rg%40mail.gmail.com.


Re: [tw5] Lost two weeks of work - what I did wrong and what you can do to avoid it

2020-05-09 Thread Arlen Beiler
Ok, I understand now. That makes sense. I'm sorry to hear about this.

There is currently no indication in the browser if the server is having
trouble saving. That's not necessarily for me to decide, but if there are
others here that would be interested in that please comment here with your
suggestions. I can see where there could be value in that.

By the way, I haven't used forever, but I recommend using PM2, which has an
epic management interface and you can tell it to install itself as a
service. Just make sure you run `pm2 save` once you have everything
configured the way you want. It's a little more complex, but if you're
already used to working with servers, it should be fine. It also has pretty
epic logs.

Arlen



On Sat, May 9, 2020 at 6:09 PM Andy Redfern  wrote:

> Hi Arlen,
>
> This was on 5.1.22
>
> The issue was that running directly:
> tiddlywiki mynewwiki --listen
> had no issues. It was saving tiddlers without issue.
>
> It was when I instantiated using forever that the permissions were wrong.
>
> The error message you show was present in the forever logs, but I only saw
> that once I had lost the data and begun the investigation.
>
> Andy
>
>
> On Saturday, May 9, 2020 at 11:02:45 PM UTC+1, Arlen Beiler wrote:
>>
>> It seemed strange to me that there would be no logging for that error,
>> and that would definitely have been a bug, however in trying to reproduce
>> this, I am getting an error message.
>>
>> Sync error while processing save of '$:/StoryList': Error: EACCES:
>> permission denied, open
>> '/Users/arlen/Desktop/GitHub/TiddlyWiki5-Arlen22/data/tiddlers/$__StoryList.tid'
>>
>> And it comes every second.
>>
>> If the directory cannot be created, there is no error, but then of course
>> the tiddler fails to save.
>>
>> Can you verify that you were running tiddlywiki version 5.1.21 or 5.1.22?
>>
>> On Sat, May 9, 2020 at 5:45 PM Arlen Beiler  wrote:
>>
>>> I'm sorry to hear this. As I deal with data folders a lot, I'm
>>> investigating this and will open a PR shortly.
>>>
>>> On Sat, May 9, 2020 at 2:00 AM Andy Redfern 
>>> wrote:
>>>
>>>> Folks,
>>>>
>>>> Started using TiddlyWiki around four weeks ago. I love the friendliness
>>>> of the community and the product itself. As a long time developer, the
>>>> ability to tweak and tinker is very attractive. I can create the work flow
>>>> I want.
>>>>
>>>> Started running in a single file mode, added in using TiddlyDesktop and
>>>> then in an effort to make it work with my phone too I switched to the
>>>> NodeJS. Read a couple of the guides to using NodeJS and TiddlyWiki, and I
>>>> was off.
>>>>
>>>> Then on Friday night disaster struck and I lost 2 weeks of data –
>>>> everything since I had switched to NodeJS. So after a day sobbing quietly
>>>> in the corner this is my effort to figure out where I went wrong with my
>>>> set up so you too don’t make the mistake I do.
>>>>
>>>> So following this guide
>>>> https://www.npmjs.com/package/tiddlywiki
>>>>
>>>> and everything worked as expected apart from
>>>> tiddlywiki mynewwiki --init server
>>>>
>>>> which errored:
>>>> Error: Error creating directory 'testlife'
>>>>
>>>> Doh! Permissions I thought. So added in Sudo
>>>> sudo tiddlywiki mynewwiki --init server
>>>>
>>>> Created fine and started
>>>> tiddlywiki mynewwiki --init server
>>>>
>>>> However it errored too:
>>>> Sync error while processing save of '$:/StoryList': Error: ENOENT: no
>>>> such file or directory, open
>>>> '/var/www/html/..fullpath../tiddlers/$__StoryList.tid'
>>>>
>>>> Ah tiddlers folder not created – manually created and I was off.
>>>>
>>>> All worked as expected except I get having to start tiddlywiki every
>>>> time my Putty session ended. Not what I wanted.
>>>> Read around nodejs advice sites and people suggest using forever.
>>>> So:
>>>> forever start --spinSleepTime 1 /usr/local/bin/tiddlywiki
>>>> /var/www/html/..fullpath../mynewwiki --listen host=0.0.0.0 username=
>>>> password=
>>>>
>>>> Everything works as I am expecting.
>>>>
>>>> And yet I have made an error – I created the Tiddler folder using Root as
>>>> I used sudo – and the new folder doesn’t have write permiss

Re: [tw5] Lost two weeks of work - what I did wrong and what you can do to avoid it

2020-05-09 Thread Arlen Beiler
Do you see any messages like this?

 syncer-server-filesystem: Dispatching 'save' task: $:/StoryList or any
other tiddler title

On Sat, May 9, 2020 at 6:02 PM Arlen Beiler  wrote:

> It seemed strange to me that there would be no logging for that error, and
> that would definitely have been a bug, however in trying to reproduce this,
> I am getting an error message.
>
> Sync error while processing save of '$:/StoryList': Error: EACCES:
> permission denied, open
> '/Users/arlen/Desktop/GitHub/TiddlyWiki5-Arlen22/data/tiddlers/$__StoryList.tid'
>
> And it comes every second.
>
> If the directory cannot be created, there is no error, but then of course
> the tiddler fails to save.
>
> Can you verify that you were running tiddlywiki version 5.1.21 or 5.1.22?
>
> On Sat, May 9, 2020 at 5:45 PM Arlen Beiler  wrote:
>
>> I'm sorry to hear this. As I deal with data folders a lot, I'm
>> investigating this and will open a PR shortly.
>>
>> On Sat, May 9, 2020 at 2:00 AM Andy Redfern  wrote:
>>
>>> Folks,
>>>
>>> Started using TiddlyWiki around four weeks ago. I love the friendliness
>>> of the community and the product itself. As a long time developer, the
>>> ability to tweak and tinker is very attractive. I can create the work flow
>>> I want.
>>>
>>> Started running in a single file mode, added in using TiddlyDesktop and
>>> then in an effort to make it work with my phone too I switched to the
>>> NodeJS. Read a couple of the guides to using NodeJS and TiddlyWiki, and I
>>> was off.
>>>
>>> Then on Friday night disaster struck and I lost 2 weeks of data –
>>> everything since I had switched to NodeJS. So after a day sobbing quietly
>>> in the corner this is my effort to figure out where I went wrong with my
>>> set up so you too don’t make the mistake I do.
>>>
>>> So following this guide
>>> https://www.npmjs.com/package/tiddlywiki
>>>
>>> and everything worked as expected apart from
>>> tiddlywiki mynewwiki --init server
>>>
>>> which errored:
>>> Error: Error creating directory 'testlife'
>>>
>>> Doh! Permissions I thought. So added in Sudo
>>> sudo tiddlywiki mynewwiki --init server
>>>
>>> Created fine and started
>>> tiddlywiki mynewwiki --init server
>>>
>>> However it errored too:
>>> Sync error while processing save of '$:/StoryList': Error: ENOENT: no
>>> such file or directory, open
>>> '/var/www/html/..fullpath../tiddlers/$__StoryList.tid'
>>>
>>> Ah tiddlers folder not created – manually created and I was off.
>>>
>>> All worked as expected except I get having to start tiddlywiki every
>>> time my Putty session ended. Not what I wanted.
>>> Read around nodejs advice sites and people suggest using forever.
>>> So:
>>> forever start --spinSleepTime 1 /usr/local/bin/tiddlywiki
>>> /var/www/html/..fullpath../mynewwiki --listen host=0.0.0.0 username=
>>> password=
>>>
>>> Everything works as I am expecting.
>>>
>>> And yet I have made an error – I created the Tiddler folder using Root as
>>> I used sudo – and the new folder doesn’t have write permissions for the
>>> process running in with forever. Without forever it has all the
>>> permissions it needs, but with forever it doesn’t.
>>>
>>> So everything looked fine – but actually Tiddlywiki was syncing to the
>>> server fine but all my data was in memory. So when after 2 weeks I stopped
>>> the process to make some tweaks ready for a proposed PR on the core code, I
>>> lost everything. 
>>>
>>>
>>> So in summary - What should I have done differently to avoid the
>>> permissions based errors in the first place?
>>>
>>> Tiddlywiki --init failed – so I used sudo – what should I have done?
>>>
>>> Tiddlywiki --init failed to create tiddlers sub folder – permissions?
>>>
>>> Forever runs as the correct user but without the permissions. I solved
>>> the problem by giving the folder 777 full write permissions, but what
>>> should I have done?
>>>
>>> Final thought. The permissions error in writing data to the server drive
>>> surfaced no errors in TW – why? Shouldn’t it have alerted me that no data
>>> was being saved. The only place I could find the error was in the difficult
>>> to interpret forever logs which I was scouring to figure where I had gone
>>> wrong.
>>>
>>> An

Re: [tw5] Lost two weeks of work - what I did wrong and what you can do to avoid it

2020-05-09 Thread Arlen Beiler
It seemed strange to me that there would be no logging for that error, and
that would definitely have been a bug, however in trying to reproduce this,
I am getting an error message.

Sync error while processing save of '$:/StoryList': Error: EACCES:
permission denied, open
'/Users/arlen/Desktop/GitHub/TiddlyWiki5-Arlen22/data/tiddlers/$__StoryList.tid'

And it comes every second.

If the directory cannot be created, there is no error, but then of course
the tiddler fails to save.

Can you verify that you were running tiddlywiki version 5.1.21 or 5.1.22?

On Sat, May 9, 2020 at 5:45 PM Arlen Beiler  wrote:

> I'm sorry to hear this. As I deal with data folders a lot, I'm
> investigating this and will open a PR shortly.
>
> On Sat, May 9, 2020 at 2:00 AM Andy Redfern  wrote:
>
>> Folks,
>>
>> Started using TiddlyWiki around four weeks ago. I love the friendliness
>> of the community and the product itself. As a long time developer, the
>> ability to tweak and tinker is very attractive. I can create the work flow
>> I want.
>>
>> Started running in a single file mode, added in using TiddlyDesktop and
>> then in an effort to make it work with my phone too I switched to the
>> NodeJS. Read a couple of the guides to using NodeJS and TiddlyWiki, and I
>> was off.
>>
>> Then on Friday night disaster struck and I lost 2 weeks of data –
>> everything since I had switched to NodeJS. So after a day sobbing quietly
>> in the corner this is my effort to figure out where I went wrong with my
>> set up so you too don’t make the mistake I do.
>>
>> So following this guide
>> https://www.npmjs.com/package/tiddlywiki
>>
>> and everything worked as expected apart from
>> tiddlywiki mynewwiki --init server
>>
>> which errored:
>> Error: Error creating directory 'testlife'
>>
>> Doh! Permissions I thought. So added in Sudo
>> sudo tiddlywiki mynewwiki --init server
>>
>> Created fine and started
>> tiddlywiki mynewwiki --init server
>>
>> However it errored too:
>> Sync error while processing save of '$:/StoryList': Error: ENOENT: no
>> such file or directory, open
>> '/var/www/html/..fullpath../tiddlers/$__StoryList.tid'
>>
>> Ah tiddlers folder not created – manually created and I was off.
>>
>> All worked as expected except I get having to start tiddlywiki every time
>> my Putty session ended. Not what I wanted.
>> Read around nodejs advice sites and people suggest using forever.
>> So:
>> forever start --spinSleepTime 1 /usr/local/bin/tiddlywiki
>> /var/www/html/..fullpath../mynewwiki --listen host=0.0.0.0 username=
>> password=
>>
>> Everything works as I am expecting.
>>
>> And yet I have made an error – I created the Tiddler folder using Root as
>> I used sudo – and the new folder doesn’t have write permissions for the
>> process running in with forever. Without forever it has all the
>> permissions it needs, but with forever it doesn’t.
>>
>> So everything looked fine – but actually Tiddlywiki was syncing to the
>> server fine but all my data was in memory. So when after 2 weeks I stopped
>> the process to make some tweaks ready for a proposed PR on the core code, I
>> lost everything. 
>>
>>
>> So in summary - What should I have done differently to avoid the
>> permissions based errors in the first place?
>>
>> Tiddlywiki --init failed – so I used sudo – what should I have done?
>>
>> Tiddlywiki --init failed to create tiddlers sub folder – permissions?
>>
>> Forever runs as the correct user but without the permissions. I solved
>> the problem by giving the folder 777 full write permissions, but what
>> should I have done?
>>
>> Final thought. The permissions error in writing data to the server drive
>> surfaced no errors in TW – why? Shouldn’t it have alerted me that no data
>> was being saved. The only place I could find the error was in the difficult
>> to interpret forever logs which I was scouring to figure where I had gone
>> wrong.
>>
>> Anyway, sorry for the long read but I hope my experience can help others
>> avoid the same issue and potentially see TW amended to report when it can’t
>> save tiddlers to the server drive.
>>
>> Andy
>>
>>
>> --
>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>> To view this discussion on the web vis

Re: [tw5] Lost two weeks of work - what I did wrong and what you can do to avoid it

2020-05-09 Thread Arlen Beiler
I'm sorry to hear this. As I deal with data folders a lot, I'm
investigating this and will open a PR shortly.

On Sat, May 9, 2020 at 2:00 AM Andy Redfern  wrote:

> Folks,
>
> Started using TiddlyWiki around four weeks ago. I love the friendliness of
> the community and the product itself. As a long time developer, the ability
> to tweak and tinker is very attractive. I can create the work flow I want.
>
> Started running in a single file mode, added in using TiddlyDesktop and
> then in an effort to make it work with my phone too I switched to the
> NodeJS. Read a couple of the guides to using NodeJS and TiddlyWiki, and I
> was off.
>
> Then on Friday night disaster struck and I lost 2 weeks of data –
> everything since I had switched to NodeJS. So after a day sobbing quietly
> in the corner this is my effort to figure out where I went wrong with my
> set up so you too don’t make the mistake I do.
>
> So following this guide
> https://www.npmjs.com/package/tiddlywiki
>
> and everything worked as expected apart from
> tiddlywiki mynewwiki --init server
>
> which errored:
> Error: Error creating directory 'testlife'
>
> Doh! Permissions I thought. So added in Sudo
> sudo tiddlywiki mynewwiki --init server
>
> Created fine and started
> tiddlywiki mynewwiki --init server
>
> However it errored too:
> Sync error while processing save of '$:/StoryList': Error: ENOENT: no such
> file or directory, open
> '/var/www/html/..fullpath../tiddlers/$__StoryList.tid'
>
> Ah tiddlers folder not created – manually created and I was off.
>
> All worked as expected except I get having to start tiddlywiki every time
> my Putty session ended. Not what I wanted.
> Read around nodejs advice sites and people suggest using forever.
> So:
> forever start --spinSleepTime 1 /usr/local/bin/tiddlywiki
> /var/www/html/..fullpath../mynewwiki --listen host=0.0.0.0 username=
> password=
>
> Everything works as I am expecting.
>
> And yet I have made an error – I created the Tiddler folder using Root as
> I used sudo – and the new folder doesn’t have write permissions for the
> process running in with forever. Without forever it has all the
> permissions it needs, but with forever it doesn’t.
>
> So everything looked fine – but actually Tiddlywiki was syncing to the
> server fine but all my data was in memory. So when after 2 weeks I stopped
> the process to make some tweaks ready for a proposed PR on the core code, I
> lost everything. 
>
>
> So in summary - What should I have done differently to avoid the
> permissions based errors in the first place?
>
> Tiddlywiki --init failed – so I used sudo – what should I have done?
>
> Tiddlywiki --init failed to create tiddlers sub folder – permissions?
>
> Forever runs as the correct user but without the permissions. I solved the
> problem by giving the folder 777 full write permissions, but what should I
> have done?
>
> Final thought. The permissions error in writing data to the server drive
> surfaced no errors in TW – why? Shouldn’t it have alerted me that no data
> was being saved. The only place I could find the error was in the difficult
> to interpret forever logs which I was scouring to figure where I had gone
> wrong.
>
> Anyway, sorry for the long read but I hope my experience can help others
> avoid the same issue and potentially see TW amended to report when it can’t
> save tiddlers to the server drive.
>
> Andy
>
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/af0978d5-310a-4094-b800-78e4267bace1%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSVeomxVdvURJ6QKS0am0JYwgHSOd_t4836Ffn45Wpo9g%40mail.gmail.com.


Re: [tw5] WebServer API error on PUT

2020-05-07 Thread Arlen Beiler
If you try creating a tiddler in the regular wiki and inspect the network
request you'll notice there is an x-requested-with header there. That is
there to keep random requests from accidentally putting tiddlers. So if you
copy that value into your request you should be good to go.

On Thu, May 7, 2020, 07:33 Brian C  wrote:

> I  started my tiddlywiki server with no username/password.  All the GET
> commands work just fine.
> But when I send a basic PUT request to create a tiddler, I am getting:
>
> HTTP/1.1 403 'X-Requested-With' header required to login to 'Brian's Space'
>
>
>
> -Brian
>
>
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/f38ef08d-9cc9-4e25-a5eb-a32088d88684%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSThABsPELcBWoEOGHE8hSMr64_mL%2Be-8HxdkRQsgy__Sg%40mail.gmail.com.


Re: [tw5] Keeping my Node.js TW instance's open tiddler state local to a device (or even browser tab)

2020-05-04 Thread Arlen Beiler
Leave the current text in there and just add that to the end.

On Mon, May 4, 2020 at 9:26 AM Arlen Beiler  wrote:

> I apologize. The sync filter is actually a core syncer feature, not a
> plugin syncadaptor feature.
>
> Add " -[[$:/StoryList]]" to the end of $:/config/SyncFilter. Make sure
> you include the space in between.
>
> On Mon, May 4, 2020 at 9:01 AM Arlen Beiler  wrote:
>
>> Hello, yes this is expected behavior and it has been in tiddlywiki for
>> many versions. The TiddlyWeb adapter plugin specifies the sync filter I
>> believe. In any case you seen you simply need to add " -$:/StoryList" to
>> the end of the active sync filter.  This problem is only related to the
>> server side of things. Single file wikis do not use this mechanism.
>>
>> On Sat, May 2, 2020, 17:48 Hugo Saavedra  wrote:
>>
>>> Hi all!
>>>
>>> I apologize if this question has been asked before -- I'm not totally
>>> sure what strings to search on, and I've scoured the TW docs pretty
>>> thoroughly.
>>>
>>> *Question*
>>>
>>> Is it possible to make it so that the state of my Wiki (specifically,
>>> which tiddlers are open) is local to the device? If so, how does one d?o
>>> this
>>>
>>> *Background*
>>>
>>> I notice that the Tiddlers that are open for me in one browser tab are
>>> open for me in all other tabs, in all other devices.
>>>
>>> When I open TiddlyWiki on a brand new device, my default "Home" page
>>> will be open momentarily, and then suddenly all the Tiddlers I have open
>>> (including drafts!) on some tab on a completely different device will open.
>>>
>>> I have been using TiddlyWiki as a repository for my math notes using the
>>> Node.js server.
>>>
>>> An important condition for me is that my server is accessible from
>>> different devices, so I am hosting it behind NGINX on a DO droplet.
>>>
>>> Write access is private with an authenticated user, read access is
>>> public.
>>>
>>> --
>>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/136d622e-4ef8-453b-84b9-2be5ad36a671%40googlegroups.com
>>> <https://groups.google.com/d/msgid/tiddlywiki/136d622e-4ef8-453b-84b9-2be5ad36a671%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSrHwmdca-qRfjn7MFFP8UQMkMB6QTSWmVGhkcMH9HBLg%40mail.gmail.com.


Re: [tw5] Keeping my Node.js TW instance's open tiddler state local to a device (or even browser tab)

2020-05-04 Thread Arlen Beiler
I apologize. The sync filter is actually a core syncer feature, not a
plugin syncadaptor feature.

Add " -[[$:/StoryList]]" to the end of $:/config/SyncFilter. Make sure you
include the space in between.

On Mon, May 4, 2020 at 9:01 AM Arlen Beiler  wrote:

> Hello, yes this is expected behavior and it has been in tiddlywiki for
> many versions. The TiddlyWeb adapter plugin specifies the sync filter I
> believe. In any case you seen you simply need to add " -$:/StoryList" to
> the end of the active sync filter.  This problem is only related to the
> server side of things. Single file wikis do not use this mechanism.
>
> On Sat, May 2, 2020, 17:48 Hugo Saavedra  wrote:
>
>> Hi all!
>>
>> I apologize if this question has been asked before -- I'm not totally
>> sure what strings to search on, and I've scoured the TW docs pretty
>> thoroughly.
>>
>> *Question*
>>
>> Is it possible to make it so that the state of my Wiki (specifically,
>> which tiddlers are open) is local to the device? If so, how does one d?o
>> this
>>
>> *Background*
>>
>> I notice that the Tiddlers that are open for me in one browser tab are
>> open for me in all other tabs, in all other devices.
>>
>> When I open TiddlyWiki on a brand new device, my default "Home" page will
>> be open momentarily, and then suddenly all the Tiddlers I have open
>> (including drafts!) on some tab on a completely different device will open.
>>
>> I have been using TiddlyWiki as a repository for my math notes using the
>> Node.js server.
>>
>> An important condition for me is that my server is accessible from
>> different devices, so I am hosting it behind NGINX on a DO droplet.
>>
>> Write access is private with an authenticated user, read access is public.
>>
>> --
>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/136d622e-4ef8-453b-84b9-2be5ad36a671%40googlegroups.com
>> <https://groups.google.com/d/msgid/tiddlywiki/136d622e-4ef8-453b-84b9-2be5ad36a671%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQnG906tJGEv2_%2BNbAA8piqmd0%3De8qUYo-8BL%3Du%3D1c5yg%40mail.gmail.com.


Re: [tw5] Keeping my Node.js TW instance's open tiddler state local to a device (or even browser tab)

2020-05-04 Thread Arlen Beiler
Hello, yes this is expected behavior and it has been in tiddlywiki for many
versions. The TiddlyWeb adapter plugin specifies the sync filter I believe.
In any case you seen you simply need to add " -$:/StoryList" to the end of
the active sync filter.  This problem is only related to the server side of
things. Single file wikis do not use this mechanism.

On Sat, May 2, 2020, 17:48 Hugo Saavedra  wrote:

> Hi all!
>
> I apologize if this question has been asked before -- I'm not totally sure
> what strings to search on, and I've scoured the TW docs pretty thoroughly.
>
> *Question*
>
> Is it possible to make it so that the state of my Wiki (specifically,
> which tiddlers are open) is local to the device? If so, how does one d?o
> this
>
> *Background*
>
> I notice that the Tiddlers that are open for me in one browser tab are
> open for me in all other tabs, in all other devices.
>
> When I open TiddlyWiki on a brand new device, my default "Home" page will
> be open momentarily, and then suddenly all the Tiddlers I have open
> (including drafts!) on some tab on a completely different device will open.
>
> I have been using TiddlyWiki as a repository for my math notes using the
> Node.js server.
>
> An important condition for me is that my server is accessible from
> different devices, so I am hosting it behind NGINX on a DO droplet.
>
> Write access is private with an authenticated user, read access is public.
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/136d622e-4ef8-453b-84b9-2be5ad36a671%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTjDS8uvmQNxSPSeB86NFXzqFmFC%2B_7XZJEszEqwcX-wA%40mail.gmail.com.


Re: [tw5] Advice on set up for self hosted TW accessible on Mac and iOS

2020-05-04 Thread Arlen Beiler
On iOS, Quine 2 allows you to access files in your Dropbox. It also enables
autosave  Without it, you are likely to lose your changes if you switch to
a different app. You can also access your files that are being served
through TiddlyServer, but only if you are on the same network. It sounded
to me like you wanted to be able to access the files on your iPad anywhere
on the go.

On Mon, May 4, 2020, 00:15 Jared Volpe  wrote:

> Thanks for the tips. Why Quine 2 instead of just viewing in the browser?
>
> On Sunday, May 3, 2020 at 2:17:19 PM UTC-7, Arlen Beiler wrote:
>>
>> I would recommend using single file wikis. On your desktop you can use
>> TiddlyServer or TiddlyDesktop to access them. Use Dropbox to sync your
>> folders. And use Quine 2 on iOS to access the files in your dropbox app
>> through the iOS files integration system. Quine 2 allows you to directly
>> access your dropbox files and edit wikis and the changes are saved
>> immediately because Dropbox integrates with the iOS file explorer.
>>
>> On Sun, May 3, 2020 at 4:54 PM Jared Volpe  wrote:
>>
>>> Sorry if this question has been asked and answered before, but I’d like
>>> the latest and greatest instructions and best practices for setting up TW
>>> for use on a Mac and iOS and I want to access it at home and away. I’m
>>> happy to use TW in Chrome. No need for dedicated apps. I do want to have my
>>> TW secured but it would be nice to not have to log in frequently. I want my
>>> TW to automatically save backups and it sounds like I can use the plugin
>>> for this but I’d like guidance for whichever solution. I’m happy to host on
>>> AWS or Google Cloud and use one of the Node versions (Node.js or
>>> TiddlyServer) or just use a service like Dropbox or preferably Google Drive
>>> or even GitHub or GitLab. Thanks for chiming in!
>>>
>>> --
>>> 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 tiddl...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/3bf711e4-2f56-49db-a5c9-8f29dd6268c2%40googlegroups.com
>>> .
>>>
>> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/286df8b4-e481-4f6c-96be-6b06b15804d2%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/286df8b4-e481-4f6c-96be-6b06b15804d2%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSkvSTCdXKyAEdEyuqwyJknhGJvf3M796i90dsV9AfFdw%40mail.gmail.com.


Re: [tw5] Re: Can't Make Upgrade From 5.1.21 to 5.2.22 Happen (node.js)

2020-05-03 Thread Arlen Beiler
Yeah, which would also explain why there is no tiddlywiki command on your
$PATH.

The --version command will give you the package.json version, which means
that it should be more accurate than npm show version

It does seem like there's a few problems with your npm install, I think.
That's probably where I would look next.

On Sun, May 3, 2020 at 9:35 PM Kevin Kleinfelter <
kleinfelter.gro...@gmail.com> wrote:

> Update: The problem has nothing to do with my tiddlers. It looks like
> somehow npm is broken on my system.
>
>- cd /tmp
>- mkdir node_modules
>-
>
>npm install tiddlywiki@5.1.21
>-
>
>node ./node_modules/tiddlywiki/tiddlywiki.js --version
>-
>
>-- It reports 5.1.21, as expected
>-
>
>npm upgrade tiddlywiki@5.1.22
>-
>
>-- It silently completes.  $? is 0, indicating success.
>-
>
>node ./node_modules/tiddlywiki/tiddlywiki.js --version
>-
>
>-- It reports 5.1.21
>
> For whatever reason, "npm upgrade" simply does not work on my system.
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/55422dcf-5914-46c8-8104-d60f08c7c0ed%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSR0SO%2B0YeeD%3D3RK1k-TATT6jygi%2BpkWHGMTheym6Bx6Yg%40mail.gmail.com.


Re: [tw5] Re: Can't Make Upgrade From 5.1.21 to 5.2.22 Happen (node.js)

2020-05-03 Thread Arlen Beiler
You must have edited a few core tiddlers and maybe added a few buttons?

I'm not sure if you changed the images intentionally or not.

I notice you have two ViewTemplate files, one with two dots before the
extension instead of one.

If none of these changes were intentional you can delete all of them.
Normally when I make custom buttons and stuff I name it a different prefix
like $:/arlen/ unless I actually need to override a core tiddler. This
helps to keep upgrade cleaner. I'm not seeing anything here yet that should
be affecting it.

On Sun, May 3, 2020 at 8:25 PM Kevin Kleinfelter <
kleinfelter.gro...@gmail.com> wrote:

> *kevin@boxtop3*:*/data/containers/tiddlywiki/data*$ find . -print | grep
> __core
>
> ./pkb/tiddlers/$*__core*_images_right-arrow.tid
>
> ./pkb/tiddlers/$*__core*_images_cancel-button.tid
>
> ./pkb/tiddlers/$*__core*_ui_Buttons_more-page-actions.tid
>
> ./pkb/tiddlers/$*__core*_images_new-journal-button.tid
>
> ./pkb/tiddlers/$*__core*_ui_ViewTemplate..tid
>
> ./pkb/tiddlers/$*__core*_images_menu-button.tid
>
> ./pkb/tiddlers/$*__core*_ui_Buttons_cancel-and-close.tid
>
> ./pkb/tiddlers/$*__core*_images_edit-button.tid
>
> ./pkb/tiddlers/$*__core*_images_new-button.tid
>
> ./pkb/tiddlers/$__config_ViewToolbarButtons_Visibility_$*__core*
> _ui_Buttons_close-others.tid
>
> ./pkb/tiddlers/$*__core*_images_done-button.tid
>
> ./pkb/tiddlers/$*__core*_images_delete-button.tid
>
> ./pkb/tiddlers/$*__core*_images_save-button.tid
>
> ./pkb/tiddlers/$*__core*_images_left-arrow.tid
>
> ./pkb/tiddlers/$__config_PageControlButtons_Visibility_$*__core*
> _ui_Buttons_advanced-search.tid
>
> ./pkb/tiddlers/$*__core*_images_close-button.tid
>
> ./pkb/tiddlers/$*__core*_images_new-image-button.tid
>
> ./pkb/tiddlers/$*__core*_images_down-arrow.tid
>
> ./pkb/tiddlers/$*__core*_images_up-arrow.tid
>
> ./pkb/tiddlers/$*__core*_ui_Buttons_save-and-close.tid
>
> ./pkb/tiddlers/$*__core*_images_advanced-search-button.tid
>
> ./pkb/tiddlers/$*__core*_images_export-button.tid
>
> ./pkb/tiddlers/$*__core*_images_options-button.tid
>
> ./pkb/tiddlers/$*__core*_ui_ViewTemplate.tid
>
> ./dtl/tiddlers/$*__core*_images_advanced-search-button.tid
>
> ./dtl/tiddlers/$*__core*_images_left-arrow.tid
>
> ./dtl/tiddlers/$__config_ViewToolbarButtons_Visibility_$*__core*
> _ui_Buttons_close-others.tid
>
> ./dtl/tiddlers/$__config_PageControlButtons_Visibility_$*__core*
> _ui_Buttons_advanced-search.tid
>
> ./dtl/tiddlers/$*__core*_images_delete-button.tid
>
> ./dtl/tiddlers/$*__core*_images_down-arrow.tid
>
> ./dtl/tiddlers/$*__core*_ui_Buttons_more-page-actions.tid
>
> ./dtl/tiddlers/$*__core*_images_new-image-button.tid
>
> ./dtl/tiddlers/$*__core*_images_new-journal-button.tid
>
> ./dtl/tiddlers/$*__core*_images_save-button.tid
>
> ./dtl/tiddlers/$*__core*_images_cancel-button.tid
>
> ./dtl/tiddlers/$*__core*_images_export-button.tid
>
> ./dtl/tiddlers/$*__core*_images_menu-button.tid
>
> ./dtl/tiddlers/$*__core*_images_up-arrow.tid
>
> ./dtl/tiddlers/$*__core*_images_edit-button.tid
>
> ./dtl/tiddlers/$*__core*_ui_Buttons_save-and-close.tid
>
> ./dtl/tiddlers/$*__core*_ui_ViewTemplate.tid
>
> ./dtl/tiddlers/$*__core*_images_done-button.tid
>
> ./dtl/tiddlers/$*__core*_ui_Buttons_cancel-and-close.tid
>
> ./dtl/tiddlers/$*__core*_images_new-button.tid
>
> ./dtl/tiddlers/$*__core*_images_options-button.tid
>
> ./dtl/tiddlers/$*__core*_images_close-button.tid
>
> ./dtl/tiddlers/$*__core*_images_right-arrow.tid
>
> ./dtl/tiddlers/$*__core*_ui_ViewTemplate..tid
>
> On Sun, May 3, 2020 at 8:08 PM Arlen Beiler  wrote:
>
>> check if you have any files in the tiddlers folder of your data folder
>> that start with $__core
>>
>> If you do, please paste the names here.
>>
>> On Sun, May 3, 2020 at 7:00 PM Kevin Kleinfelter <
>> kleinfelter.gro...@gmail.com> wrote:
>>
>>> No output from `which tiddlywiki`.  The only way I can use a
>>> "tiddlywiki" command is to first run something like:
>>> `alias tiddlywiki=node 
>>> /usr/local/lib/node_modules/tiddlywiki/tiddlywiki.js`.
>>> So I usually run it as `node /usr/local/lib/node_modules/
>>> tiddlywiki/tiddlywiki.js`
>>>
>>> As I mentioned earlier, the only non-plugin tiddlywiki.js is
>>> /usr/local/lib/node_modules/tiddlywiki/tiddlywiki.js and that
>>> reports 5.1.22.
>>>
>>> I think it is clear that the version I HAVE after attempting to upgrade
>>> is 5.1.21, and npm is somehow broken and thinks I have 5.1.22.
>>>
>>>
>>> On Sun, May 3, 2020 at 5:12 PM Arlen Bei

Re: [tw5] Re: Can't Make Upgrade From 5.1.21 to 5.2.22 Happen (node.js)

2020-05-03 Thread Arlen Beiler
Are there any other folders in the data folder beside the tiddlers folder?


On Sun, May 3, 2020 at 8:25 PM Kevin Kleinfelter <
kleinfelter.gro...@gmail.com> wrote:

> *kevin@boxtop3*:*/data/containers/tiddlywiki/data*$ find . -print | grep
> __core
>
> ./pkb/tiddlers/$*__core*_images_right-arrow.tid
>
> ./pkb/tiddlers/$*__core*_images_cancel-button.tid
>
> ./pkb/tiddlers/$*__core*_ui_Buttons_more-page-actions.tid
>
> ./pkb/tiddlers/$*__core*_images_new-journal-button.tid
>
> ./pkb/tiddlers/$*__core*_ui_ViewTemplate..tid
>
> ./pkb/tiddlers/$*__core*_images_menu-button.tid
>
> ./pkb/tiddlers/$*__core*_ui_Buttons_cancel-and-close.tid
>
> ./pkb/tiddlers/$*__core*_images_edit-button.tid
>
> ./pkb/tiddlers/$*__core*_images_new-button.tid
>
> ./pkb/tiddlers/$__config_ViewToolbarButtons_Visibility_$*__core*
> _ui_Buttons_close-others.tid
>
> ./pkb/tiddlers/$*__core*_images_done-button.tid
>
> ./pkb/tiddlers/$*__core*_images_delete-button.tid
>
> ./pkb/tiddlers/$*__core*_images_save-button.tid
>
> ./pkb/tiddlers/$*__core*_images_left-arrow.tid
>
> ./pkb/tiddlers/$__config_PageControlButtons_Visibility_$*__core*
> _ui_Buttons_advanced-search.tid
>
> ./pkb/tiddlers/$*__core*_images_close-button.tid
>
> ./pkb/tiddlers/$*__core*_images_new-image-button.tid
>
> ./pkb/tiddlers/$*__core*_images_down-arrow.tid
>
> ./pkb/tiddlers/$*__core*_images_up-arrow.tid
>
> ./pkb/tiddlers/$*__core*_ui_Buttons_save-and-close.tid
>
> ./pkb/tiddlers/$*__core*_images_advanced-search-button.tid
>
> ./pkb/tiddlers/$*__core*_images_export-button.tid
>
> ./pkb/tiddlers/$*__core*_images_options-button.tid
>
> ./pkb/tiddlers/$*__core*_ui_ViewTemplate.tid
>
> ./dtl/tiddlers/$*__core*_images_advanced-search-button.tid
>
> ./dtl/tiddlers/$*__core*_images_left-arrow.tid
>
> ./dtl/tiddlers/$__config_ViewToolbarButtons_Visibility_$*__core*
> _ui_Buttons_close-others.tid
>
> ./dtl/tiddlers/$__config_PageControlButtons_Visibility_$*__core*
> _ui_Buttons_advanced-search.tid
>
> ./dtl/tiddlers/$*__core*_images_delete-button.tid
>
> ./dtl/tiddlers/$*__core*_images_down-arrow.tid
>
> ./dtl/tiddlers/$*__core*_ui_Buttons_more-page-actions.tid
>
> ./dtl/tiddlers/$*__core*_images_new-image-button.tid
>
> ./dtl/tiddlers/$*__core*_images_new-journal-button.tid
>
> ./dtl/tiddlers/$*__core*_images_save-button.tid
>
> ./dtl/tiddlers/$*__core*_images_cancel-button.tid
>
> ./dtl/tiddlers/$*__core*_images_export-button.tid
>
> ./dtl/tiddlers/$*__core*_images_menu-button.tid
>
> ./dtl/tiddlers/$*__core*_images_up-arrow.tid
>
> ./dtl/tiddlers/$*__core*_images_edit-button.tid
>
> ./dtl/tiddlers/$*__core*_ui_Buttons_save-and-close.tid
>
> ./dtl/tiddlers/$*__core*_ui_ViewTemplate.tid
>
> ./dtl/tiddlers/$*__core*_images_done-button.tid
>
> ./dtl/tiddlers/$*__core*_ui_Buttons_cancel-and-close.tid
>
> ./dtl/tiddlers/$*__core*_images_new-button.tid
>
> ./dtl/tiddlers/$*__core*_images_options-button.tid
>
> ./dtl/tiddlers/$*__core*_images_close-button.tid
>
> ./dtl/tiddlers/$*__core*_images_right-arrow.tid
>
> ./dtl/tiddlers/$*__core*_ui_ViewTemplate..tid
>
> On Sun, May 3, 2020 at 8:08 PM Arlen Beiler  wrote:
>
>> check if you have any files in the tiddlers folder of your data folder
>> that start with $__core
>>
>> If you do, please paste the names here.
>>
>> On Sun, May 3, 2020 at 7:00 PM Kevin Kleinfelter <
>> kleinfelter.gro...@gmail.com> wrote:
>>
>>> No output from `which tiddlywiki`.  The only way I can use a
>>> "tiddlywiki" command is to first run something like:
>>> `alias tiddlywiki=node 
>>> /usr/local/lib/node_modules/tiddlywiki/tiddlywiki.js`.
>>> So I usually run it as `node /usr/local/lib/node_modules/
>>> tiddlywiki/tiddlywiki.js`
>>>
>>> As I mentioned earlier, the only non-plugin tiddlywiki.js is
>>> /usr/local/lib/node_modules/tiddlywiki/tiddlywiki.js and that
>>> reports 5.1.22.
>>>
>>> I think it is clear that the version I HAVE after attempting to upgrade
>>> is 5.1.21, and npm is somehow broken and thinks I have 5.1.22.
>>>
>>>
>>> On Sun, May 3, 2020 at 5:12 PM Arlen Beiler  wrote:
>>>
>>>> can you run `which tiddlywiki`?
>>>>
>>>> Also, is you current folder a data folder? Meaning is there a
>>>> tiddlywiki.info file in the folder you are running the tiddlywiki
>>>> command from?
>>>>
>>>> On Sun, May 3, 2020 at 1:34 PM Kevin Kleinfelter <
>>>> kleinfelter.gro...@gmail.com> wrote:
>>>>
>>>>>

Re: [tw5] Network Error Obnoxious on Chrome

2020-05-03 Thread Arlen Beiler
Ok, sounds good.

In thinking this over, I think the best idea would be for you to open an
issue on GitHub for this. If you don't have a GitHub account and don't feel
like creating one I could open it as well, but feel free to do so.

https://github.com/Jermolene/TiddlyWiki5/issues

Arlen

On Sun, May 3, 2020 at 7:59 PM Kevin Kleinfelter <
kleinfelter.gro...@gmail.com> wrote:

> I'm running with 5.1.22 now.  As I mentioned earlier, I deleted 5.1.21 and
> simply installed 5.1.22, so it is a pure 5.1.22.  (I backed up the 5.1.21,
> to be able to pursue my other question about the failed upgrade.)
>
> On Sun, May 3, 2020 at 7:50 PM Arlen Beiler  wrote:
>
>> What is the version number in the control panel. If you click the
>> gear icon it will open the control panel, and the main tab should list the
>> version.
>>
>> On Sun, May 3, 2020 at 6:54 PM Kevin Kleinfelter <
>> kleinfelter.gro...@gmail.com> wrote:
>>
>>> That's a good suggestion, but no joy.
>>>
>>> I removed and re-installed tiddlywiki with npm.  I created a new wiki,
>>> so I've got a clean tiddlywiki.info, no content and no plugins.  If I
>>> open or close a tiddler from an already-open wiki while wifi is down, the
>>> status icon turns red and start spinning its arrows, and Network Error
>>> opens (or counts upward) at the rate of about 1 per 5 seconds.  I've tested
>>> with all extensions disabled too.  Chrome version is 81.0.4044.129.
>>>
>>> Happens with Safari and Firefox.  (I was mistaken when I said it did not
>>> happen with Firefox in my earlier post.)
>>>
>>> Pretty much makes node.js TW unusable in offline mode for me. More
>>> importantly, it gets me in trouble with my wife!  ;-)
>>>
>>> On Sunday, May 3, 2020 at 5:18:42 PM UTC-4, Arlen Beiler wrote:
>>>>
>>>> This is quite possibly related to your other post. Please try creating
>>>> a new empty datafolder and only copy the tiddlywiki.info file from
>>>> your current data folder to get a clean one. Then try testing everything
>>>> again.
>>>>
>>>>>
>>>>> --
>>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/219bd1ac-216a-48db-a168-ef784ed1156c%40googlegroups.com
>>> <https://groups.google.com/d/msgid/tiddlywiki/219bd1ac-216a-48db-a168-ef784ed1156c%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/tiddlywiki/0zoa06k0OTw/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> tiddlywiki+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSoY27yh%2BQ44313AtHr7Z48ivD5yD5b9xg57xSpGqOZLg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSoY27yh%2BQ44313AtHr7Z48ivD5yD5b9xg57xSpGqOZLg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/CAKBuMvJ8%2BtB0L33Unz-HrK19Baj6BEXUbdZVn52yQrbTXXOHqg%40mail.gmail.com
> <https://groups.google.com/d/msgid/tiddlywiki/CAKBuMvJ8%2BtB0L33Unz-HrK19Baj6BEXUbdZVn52yQrbTXXOHqg%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTEMP0Zf%3DcCogDROMHEFCf29-gpVrL6GK-0JGzor8zA2Q%40mail.gmail.com.


Re: [tw5] Re: Can't Make Upgrade From 5.1.21 to 5.2.22 Happen (node.js)

2020-05-03 Thread Arlen Beiler
check if you have any files in the tiddlers folder of your data folder that
start with $__core

If you do, please paste the names here.

On Sun, May 3, 2020 at 7:00 PM Kevin Kleinfelter <
kleinfelter.gro...@gmail.com> wrote:

> No output from `which tiddlywiki`.  The only way I can use a "tiddlywiki"
> command is to first run something like:
> `alias tiddlywiki=node /usr/local/lib/node_modules/tiddlywiki/tiddlywiki.js`.
> So I usually run it as `node /usr/local/lib/node_modules/
> tiddlywiki/tiddlywiki.js`
>
> As I mentioned earlier, the only non-plugin tiddlywiki.js is
> /usr/local/lib/node_modules/tiddlywiki/tiddlywiki.js and that
> reports 5.1.22.
>
> I think it is clear that the version I HAVE after attempting to upgrade is
> 5.1.21, and npm is somehow broken and thinks I have 5.1.22.
>
>
> On Sun, May 3, 2020 at 5:12 PM Arlen Beiler  wrote:
>
>> can you run `which tiddlywiki`?
>>
>> Also, is you current folder a data folder? Meaning is there a
>> tiddlywiki.info file in the folder you are running the tiddlywiki
>> command from?
>>
>> On Sun, May 3, 2020 at 1:34 PM Kevin Kleinfelter <
>> kleinfelter.gro...@gmail.com> wrote:
>>
>>>
>>>- `node /usr/local/lib/node_modules/tiddlywiki/tiddlywiki.js
>>>--version` reports 5.1.21.
>>>- `npm show tiddlywiki version` reports 5.1.22
>>>- `find / -name tiddlywiki.js` reports:
>>>   - /usr/local/lib/node_modules/tiddlywiki/tiddlywiki.js
>>>   -
>>>   
>>> /usr/local/lib/node_modules/tiddlywiki/plugins/tiddlywiki/codemirror-mode-x-tiddlywiki/files/mode/tiddlywiki/tiddlywiki.js
>>>
>>>
>>> --
>>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/5dfa53d0-47ca-4adc-a7c4-fd3e6c5d4390%40googlegroups.com
>>> <https://groups.google.com/d/msgid/tiddlywiki/5dfa53d0-47ca-4adc-a7c4-fd3e6c5d4390%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/tiddlywiki/LKLuEaMB8vk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> tiddlywiki+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSRr%2BKbW4c5VT-w59N05qa3rGa_98v3mQj%3D35kLemAeAsQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSRr%2BKbW4c5VT-w59N05qa3rGa_98v3mQj%3D35kLemAeAsQ%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/CAKBuMvKjUHqzyL5OqrPVy1H45PrmY6w2-id%2BVgcVfLo4aC2YJA%40mail.gmail.com
> <https://groups.google.com/d/msgid/tiddlywiki/CAKBuMvKjUHqzyL5OqrPVy1H45PrmY6w2-id%2BVgcVfLo4aC2YJA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTi%2B78qEQAF7fyo%3DXSwrrK5RZYNZxgMKCaRD073NUnFKA%40mail.gmail.com.


Re: [tw5] Network Error Obnoxious on Chrome

2020-05-03 Thread Arlen Beiler
What is the version number in the control panel. If you click the gear icon
it will open the control panel, and the main tab should list the version.

On Sun, May 3, 2020 at 6:54 PM Kevin Kleinfelter <
kleinfelter.gro...@gmail.com> wrote:

> That's a good suggestion, but no joy.
>
> I removed and re-installed tiddlywiki with npm.  I created a new wiki, so
> I've got a clean tiddlywiki.info, no content and no plugins.  If I open
> or close a tiddler from an already-open wiki while wifi is down, the status
> icon turns red and start spinning its arrows, and Network Error opens (or
> counts upward) at the rate of about 1 per 5 seconds.  I've tested with all
> extensions disabled too.  Chrome version is 81.0.4044.129.
>
> Happens with Safari and Firefox.  (I was mistaken when I said it did not
> happen with Firefox in my earlier post.)
>
> Pretty much makes node.js TW unusable in offline mode for me. More
> importantly, it gets me in trouble with my wife!  ;-)
>
> On Sunday, May 3, 2020 at 5:18:42 PM UTC-4, Arlen Beiler wrote:
>>
>> This is quite possibly related to your other post. Please try creating a
>> new empty datafolder and only copy the tiddlywiki.info file from your
>> current data folder to get a clean one. Then try testing everything again.
>>
>>>
>>> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/219bd1ac-216a-48db-a168-ef784ed1156c%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/219bd1ac-216a-48db-a168-ef784ed1156c%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSoY27yh%2BQ44313AtHr7Z48ivD5yD5b9xg57xSpGqOZLg%40mail.gmail.com.


Re: [tw5] Network Error Obnoxious on Chrome

2020-05-03 Thread Arlen Beiler
This is quite possibly related to your other post. Please try creating a
new empty datafolder and only copy the tiddlywiki.info file from your
current data folder to get a clean one. Then try testing everything again.

On Sun, May 3, 2020 at 4:42 PM Kevin Kleinfelter <
kleinfelter.gro...@gmail.com> wrote:

> When network connectivity is down, the node.js edition of TW works nicely
> and as expected with Firefox.  With Chrome, the minute I open a tiddler, it
> goes nuts with the gold Network Error message.  If I close the message, it
> comes right back.  This makes the node.js TW unusable offline with Chrome.
>
> How can I get TW to show the Network Error zero or one times when using
> Chrome.
>
> Using 5.1.22.
> TIA
>
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/ec4f91c3-bcc8-4548-90df-1cb0b1cf71ea%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQ5kn-N5LsCroqsEATJionwGa%3D1Aewgjh8O0fZM7DLUiQ%40mail.gmail.com.


Re: [tw5] Advice on set up for self hosted TW accessible on Mac and iOS

2020-05-03 Thread Arlen Beiler
I would recommend using single file wikis. On your desktop you can use
TiddlyServer or TiddlyDesktop to access them. Use Dropbox to sync your
folders. And use Quine 2 on iOS to access the files in your dropbox app
through the iOS files integration system. Quine 2 allows you to directly
access your dropbox files and edit wikis and the changes are saved
immediately because Dropbox integrates with the iOS file explorer.

On Sun, May 3, 2020 at 4:54 PM Jared Volpe  wrote:

> Sorry if this question has been asked and answered before, but I’d like
> the latest and greatest instructions and best practices for setting up TW
> for use on a Mac and iOS and I want to access it at home and away. I’m
> happy to use TW in Chrome. No need for dedicated apps. I do want to have my
> TW secured but it would be nice to not have to log in frequently. I want my
> TW to automatically save backups and it sounds like I can use the plugin
> for this but I’d like guidance for whichever solution. I’m happy to host on
> AWS or Google Cloud and use one of the Node versions (Node.js or
> TiddlyServer) or just use a service like Dropbox or preferably Google Drive
> or even GitHub or GitLab. Thanks for chiming in!
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/3bf711e4-2f56-49db-a5c9-8f29dd6268c2%40googlegroups.com
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQWAgXNeQAnwXK_nT19S_oU5t%3DLGJhVBK28eqDG%2BZfGGA%40mail.gmail.com.


Re: [tw5] Re: Can't Make Upgrade From 5.1.21 to 5.2.22 Happen (node.js)

2020-05-03 Thread Arlen Beiler
can you run `which tiddlywiki`?

Also, is you current folder a data folder? Meaning is there a
tiddlywiki.info file in the folder you are running the tiddlywiki command
from?

On Sun, May 3, 2020 at 1:34 PM Kevin Kleinfelter <
kleinfelter.gro...@gmail.com> wrote:

>
>- `node /usr/local/lib/node_modules/tiddlywiki/tiddlywiki.js
>--version` reports 5.1.21.
>- `npm show tiddlywiki version` reports 5.1.22
>- `find / -name tiddlywiki.js` reports:
>   - /usr/local/lib/node_modules/tiddlywiki/tiddlywiki.js
>   -
>   
> /usr/local/lib/node_modules/tiddlywiki/plugins/tiddlywiki/codemirror-mode-x-tiddlywiki/files/mode/tiddlywiki/tiddlywiki.js
>
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/5dfa53d0-47ca-4adc-a7c4-fd3e6c5d4390%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSRr%2BKbW4c5VT-w59N05qa3rGa_98v3mQj%3D35kLemAeAsQ%40mail.gmail.com.


Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-05-01 Thread Arlen Beiler
I see. It should work the same with or without TiddlyServer, so it would be
better to start a new thread for this because I'm not really as familiar
with this part of it.

On Fri, May 1, 2020 at 5:47 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> When I try to access the JSON file, the terminal shows this:
>
> [2020-05-01T14:44:59.021-0700] GET - 127.0.0.1
> /library/recipes/library/tiddlers/%2524%253A%252Fplugins%252FMAS%252FTEST.json
> - ms - -
>
> repeatedly (I guess every 2 or 3 minutes). But the browser page is stuck
> in loading mode, nothing displayed.
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/ab4869ef-4b80-4f1e-97f2-66ea3d939ff3%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSR7GN9OQwgHHDgHz_hSnriVkESUuY1K%3DuyMhbPtHTqkWA%40mail.gmail.com.


Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-05-01 Thread Arlen Beiler
What is the request log in the terminal? Can you paste the request lines in
here?

On Fri, May 1, 2020 at 3:07 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> More testing. I added "json" as mimetype. Not sure if that was necessary.
>
> But, when I navigate with TS down the directory, I find that it can't load:
>
> %24%3A%2Fplugins%2FMAS%2FTEST.json
>
> So, maybe TS doesn't like these special characters?
>
> When I changed the name to TEST.json, then even though I can browse the
> file with either TS or http-server, I couldn't load it as a library with
> either server. So apparently the url-encoded name structure is important
> for some reason.
>
> Is there any reason that TS wouldn't be able to load files with
> url-encoded names?
>
> Thanks!
>
> On Friday, May 1, 2020 at 11:45:20 AM UTC-7, Mark S. wrote:
>>
>> I'm trying to serve up a plugin *library*. A library is an index.html
>> file with specified directories below it, and some tid files in those
>> directories. Data folders do not have to be involved at all. Just the
>> static server part of TS.
>>
>> I can accomplish this already by running http-server on node, but that
>> means I have to have two servers running (TS and http-server). It would be
>> convenient if I could just run TS. I set a virtual "library" in
>> settings.json that points to the directory containing the index.html file.
>> I put this path into the url field of a tiddler tagged
>> $:/tags/PluginLibrary. Now I can go into the plugins under control panel
>> and click on "Get More Plugins". It opens up and shows my new, personal
>> library. But when I attempt to install a plugin, it fails.
>>
>> Ok, I just ran a test. It appears that TS won't serve up JSON files. So
>> maybe my question is, how do I enable TS to serve JSON files?
>>
>> Thanks!
>>
>> On Friday, May 1, 2020 at 11:26:01 AM UTC-7, Arlen Beiler wrote:
>>>
>>> TiddlyServer will not serve files within data folders, that is the data
>>> folder's job.
>>>
>>> But it doesn't make sense that you would be trying to serve plugin
>>> tiddlers from within a data folder, so I'm not quite sure what you're
>>> asking.
>>>
>>> On Fri, May 1, 2020, 11:57 'Mark S.' via TiddlyWiki <
>>> tiddlywiki@googlegroups.com> wrote:
>>>
>>>>
>>>> I'm trying to have TS serve up a plugin library.
>>>>
>>>> Everything seems to work, except TS doesn't actually serve up the
>>>> plugin tiddlers.
>>>>
>>>> I think the problem is that TS isn't serving up static files from
>>>> sub-directories. Is there a setting that will tell TS to serve up static
>>>> files more than one level deep?
>>>>
>>>> Thanks!
>>>>
>>>>
>>>> --
>>>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/tiddlywiki/21a0177e-4165-48a4-b1b4-1db59caba7b9%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/tiddlywiki/21a0177e-4165-48a4-b1b4-1db59caba7b9%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/6d9e4ae1-70a7-422b-bc0e-54505f332b66%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/6d9e4ae1-70a7-422b-bc0e-54505f332b66%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSRS85m%2Ba0FCVBE5R1SRRt%3DfZGz0wYHxORXQp_COSqwgdg%40mail.gmail.com.


Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-05-01 Thread Arlen Beiler
TiddlyServer will not serve files within data folders, that is the data
folder's job.

But it doesn't make sense that you would be trying to serve plugin tiddlers
from within a data folder, so I'm not quite sure what you're asking.

On Fri, May 1, 2020, 11:57 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

>
> I'm trying to have TS serve up a plugin library.
>
> Everything seems to work, except TS doesn't actually serve up the plugin
> tiddlers.
>
> I think the problem is that TS isn't serving up static files from
> sub-directories. Is there a setting that will tell TS to serve up static
> files more than one level deep?
>
> Thanks!
>
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/21a0177e-4165-48a4-b1b4-1db59caba7b9%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSEMF3q%3DeQNBMGK3QfVbz98x9XumeHeoXN81mLLg1VLCA%40mail.gmail.com.


Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-04-30 Thread Arlen Beiler
Here is my reply in that issue. I also include an example tiddlywiki.info

Like I said, it's not a good idea to use the plugin library with data
folders because they won't get upgraded when you upgrade to a newer version
of TiddlyWiki. So that's probably why it's not included.

https://github.com/Arlen22/TiddlyServer/issues/94#issuecomment-622179126

On Thu, Apr 30, 2020 at 7:47 PM Arlen Beiler  wrote:

> You're the second person to ask that in the last few days. This must be a
> recent change in TiddlyWiki.
>
> Normally you specify the plugins by name in the tiddlywiki.info file so
> they get upgraded automatically when you upgrade to a new version of
> TiddlyWiki. This is definitely the better way to do it, otherwise you will
> end up running into compatibility issues between core and the official
> plugins.
>
> In any case, this would be a TiddlyWiki data folder question. It's not
> specific to TiddlyServer.
>
> Apparently you can also drag in the plugin library config tiddler.
> https://github.com/Arlen22/TiddlyServer/issues/94#issuecomment-622159672
>
> On Thu, Apr 30, 2020 at 6:45 PM 'Mark S.' via TiddlyWiki <
> tiddlywiki@googlegroups.com> wrote:
>
>> How do I tell TS where my physical plugin library and/or where do I put a
>> collection of plugins?
>>
>> Thanks!
>>
>> On Friday, April 24, 2020 at 1:39:44 PM UTC-7, Arlen Beiler wrote:
>>>
>>> Hello Everyone,
>>>
>>> I've upgraded TiddlyServer to target 5.1.22.
>>>
>>> @someguynamedmatt helped rearrange the build process, resulting in a
>>> clean production build. So, I've now published TiddlyServer to npm and you
>>> can install it by running
>>>
>>>  npm install -g tiddlyserver
>>>
>>> This will install it globally, which also puts it in your PATH, so you
>>> can run it directly using
>>>
>>>  tiddlyserver --config /path/to/settings.json
>>>
>>> Windows should also work just fine. You can use the tilde (~) if your
>>> shell supports it. I forgot to include tilde support for the config
>>> parameter (if the shell passes it through). I'll add that in the future.
>>>
>>> If you don't have npm installed or you want to do a portable install,
>>> you'll find the archives listed at
>>> https://github.com/Arlen22/TiddlyServer/releases/tag/v2.2.0-alpha-3. I
>>> downloaded the tgz files from npm, and the zip files are the same archive
>>> converted to a zip file.
>>>
>>> I've separated out the tiddlywiki bundle into a separate npm package. If
>>> you're familiar with that it's still the same idea. I will add more info to
>>> the readme, but for now it's ready to use. It also includes the client-side
>>> .js files for adding in an html page, which probably nobody uses yet. I'm
>>> still working on the use cases and so forth for that, so that's just a
>>> little teaser.
>>>
>>> https://www.npmjs.com/package/tiddlywiki-production
>>>
>>> As always, remember to create backups before upgrading.
>>>
>>> Enjoy,
>>> Arlen
>>>
>> --
>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/5ec84934-3e6c-454c-802e-4e06abd22b01%40googlegroups.com
>> <https://groups.google.com/d/msgid/tiddlywiki/5ec84934-3e6c-454c-802e-4e06abd22b01%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQKc4R5%3Dwc_%3DEk1C2qEQL3eiErqWLVwwGh%3DSJ%3D%3DVUCO%3Dw%40mail.gmail.com.


Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-04-30 Thread Arlen Beiler
You're the second person to ask that in the last few days. This must be a
recent change in TiddlyWiki.

Normally you specify the plugins by name in the tiddlywiki.info file so
they get upgraded automatically when you upgrade to a new version of
TiddlyWiki. This is definitely the better way to do it, otherwise you will
end up running into compatibility issues between core and the official
plugins.

In any case, this would be a TiddlyWiki data folder question. It's not
specific to TiddlyServer.

Apparently you can also drag in the plugin library config tiddler.
https://github.com/Arlen22/TiddlyServer/issues/94#issuecomment-622159672

On Thu, Apr 30, 2020 at 6:45 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> How do I tell TS where my physical plugin library and/or where do I put a
> collection of plugins?
>
> Thanks!
>
> On Friday, April 24, 2020 at 1:39:44 PM UTC-7, Arlen Beiler wrote:
>>
>> Hello Everyone,
>>
>> I've upgraded TiddlyServer to target 5.1.22.
>>
>> @someguynamedmatt helped rearrange the build process, resulting in a
>> clean production build. So, I've now published TiddlyServer to npm and you
>> can install it by running
>>
>>  npm install -g tiddlyserver
>>
>> This will install it globally, which also puts it in your PATH, so you
>> can run it directly using
>>
>>  tiddlyserver --config /path/to/settings.json
>>
>> Windows should also work just fine. You can use the tilde (~) if your
>> shell supports it. I forgot to include tilde support for the config
>> parameter (if the shell passes it through). I'll add that in the future.
>>
>> If you don't have npm installed or you want to do a portable install,
>> you'll find the archives listed at
>> https://github.com/Arlen22/TiddlyServer/releases/tag/v2.2.0-alpha-3. I
>> downloaded the tgz files from npm, and the zip files are the same archive
>> converted to a zip file.
>>
>> I've separated out the tiddlywiki bundle into a separate npm package. If
>> you're familiar with that it's still the same idea. I will add more info to
>> the readme, but for now it's ready to use. It also includes the client-side
>> .js files for adding in an html page, which probably nobody uses yet. I'm
>> still working on the use cases and so forth for that, so that's just a
>> little teaser.
>>
>> https://www.npmjs.com/package/tiddlywiki-production
>>
>> As always, remember to create backups before upgrading.
>>
>> Enjoy,
>> Arlen
>>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/5ec84934-3e6c-454c-802e-4e06abd22b01%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/5ec84934-3e6c-454c-802e-4e06abd22b01%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdST9t%3DY62qox4zpLU7D4HbZG2SF%2BqAf_0n1A%3DiRewckW_g%40mail.gmail.com.


Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

2020-04-30 Thread Arlen Beiler
If I was doing that I would auto assign an integer primary key, but if
that's more work you could use the created timestamp.

On Thu, Apr 30, 2020 at 8:40 AM ludwa6  wrote:

> Arlen: storage in a RDBMS (requirement for this application i want to
> develop[1]) requires a Primary Key that is both guaranteed unique AND
> cannot be changed -but tiddler Title *can* be changed, so that is not a
> good candidate, seems to me. The one element of this schema that appears
> immutable to me is that "created" date/time stamp, which has 3 digits
> beyond minutes (thousandths of a minute, perhaps?), so that is fine-grained
> enough to guarantee uniqueness, i guess.
>
> [1] To explain: i need RDBMS storage for this particular application
> because i need to correlate tiddlers with records in other tables of the
> database that they are meant to document, or otherwise extend. This RDBMS
> lies at the heart of a gateway that facilitates data I/O with a set remote
> nodes for sensing & control of farm operations -initially a
> climate-controlled greenhouse.  The data flowing between nodes in this
> environment is structured as a rule, such that humans cannot mess with it.
> Yet it is precisely those "messy" human inputs -e.g. observations, photos,
> links, questions, etc.- that i aim to capture thru TiddlyWiki.  The real
> power of this application will lie in its ability to corrrelate machine
> data with user-generated data... And for that, i need both to be stored in
> RDBMS (just in case you were wondering why :-)
>
>
> On Thursday, April 30, 2020 at 12:23:00 PM UTC+1, Arlen Beiler wrote:
>>
>> Those last lines are a mystery to me. I've never seen them before. I'll
>> check make sure I'm not missing anything.
>>
>> The tiddler title is the primary key in Tiddly wiki. I don't really think
>> you would need to store it anywhere else though.
>>
>> Everything is in flux right now, but hopefully we'll have it mailed down
>> soon and then I'll be able to better recommend how to use a database with
>> this. But it certainly isn't required.
>>
>> On Thu, Apr 30, 2020, 06:42 ludwa6  wrote:
>>
>>> Arlen: Putting your earlier instructions together with Mark's
>>> declaration of listener port, i *think* i've got he server running on my Pi
>>> server... But in fact i'm still confused about this.
>>>
>>> The UI looks & seems to be performing pretty much like TiddlyWiki
>>> single-file version, except that default "Getting Started" tiddler asked me
>>> to make & save one, & confirm that it worked... So i did, and now i see it
>>> in the file system, inside 'MyNewWikiFolder/tiddlers/ , along with
>>> $_StoryList.tid .  I then created a 2nd tiddler, which appeared as a 2nd
>>> file in the same directory... So can i safely presume i've got tiddly
>>> server working as it should?
>>>
>>> Now looking at the schema of these files, it seems pretty simple, i.e.:
>>>
>>>- created: (date/time stamp in mmddhhmm format, followed by a
>>>3-digit numeric)
>>>- modified: (same format as above)
>>>- tags: (if any, a horizontal list)
>>>- title: (as declared)
>>>- type: text/vnd.tiddlywiki
>>>- (single line space, followed by...
>>>- (full text of tiddler, followed by...
>>>- (some 16 lines, blank except for '~' as initial character...
>>>- >>- [noeol] 7L, 132C  7,23  ALL
>>>
>>> That last line is most mysterious to me, as i don't know what those
>>> codes refer to, nor why there's so many spaces preceding the last 2
>>> strings.
>>>
>>> Best candidate for Primary Key here, as far as i can see, would be the
>>> first attribute -the "created" date/time stamp- but i don't know how to
>>> turn these files into rows in the SQLite database where i want to store the
>>> data. From what Tony said, i gather it would involve building a sync module
>>> of some sort, but i have no idea how that might be done.  Any prior art, or
>>> ideas about this?
>>>
>>>
>>>
>>> On Wednesday, April 29, 2020 at 7:00:25 PM UTC+1, Arlen Beiler wrote:
>>>>
>>>> Sorry, what I said was for tiddly server. What mark said is for tiddly
>>>> wiki.
>>>>
>>>> On Wed, Apr 29, 2020, 13:56 'Mark S.' via TiddlyWiki <
>>>> tiddl...@googlegroups.com> wrote:
>>>>
>>>>>
>>>>> The listen command can take a port number. Like
>>>>>
>>>>> --

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

2020-04-30 Thread Arlen Beiler
Yes, if they're properly showing up in the folder then everything is
working. Data folders are the second officially supported format in
tiddlywiki, after single file wikis. So feel free to just use the data
folder, in my opinion you don't need to store it anywhere else.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQ_DkPJnrZ0ZPvrq677_vcAfcqo1A6vM9WgPh5jGzXghw%40mail.gmail.com.


Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

2020-04-30 Thread Arlen Beiler
Those last lines are a mystery to me. I've never seen them before. I'll
check make sure I'm not missing anything.

The tiddler title is the primary key in Tiddly wiki. I don't really think
you would need to store it anywhere else though.

Everything is in flux right now, but hopefully we'll have it mailed down
soon and then I'll be able to better recommend how to use a database with
this. But it certainly isn't required.

On Thu, Apr 30, 2020, 06:42 ludwa6  wrote:

> Arlen: Putting your earlier instructions together with Mark's declaration
> of listener port, i *think* i've got he server running on my Pi server...
> But in fact i'm still confused about this.
>
> The UI looks & seems to be performing pretty much like TiddlyWiki
> single-file version, except that default "Getting Started" tiddler asked me
> to make & save one, & confirm that it worked... So i did, and now i see it
> in the file system, inside 'MyNewWikiFolder/tiddlers/ , along with
> $_StoryList.tid .  I then created a 2nd tiddler, which appeared as a 2nd
> file in the same directory... So can i safely presume i've got tiddly
> server working as it should?
>
> Now looking at the schema of these files, it seems pretty simple, i.e.:
>
>- created: (date/time stamp in mmddhhmm format, followed by a
>3-digit numeric)
>- modified: (same format as above)
>- tags: (if any, a horizontal list)
>- title: (as declared)
>- type: text/vnd.tiddlywiki
>- (single line space, followed by...
>- (full text of tiddler, followed by...
>- (some 16 lines, blank except for '~' as initial character...
>- - [noeol] 7L, 132C  7,23  ALL
>
> That last line is most mysterious to me, as i don't know what those codes
> refer to, nor why there's so many spaces preceding the last 2 strings.
>
> Best candidate for Primary Key here, as far as i can see, would be the
> first attribute -the "created" date/time stamp- but i don't know how to
> turn these files into rows in the SQLite database where i want to store the
> data. From what Tony said, i gather it would involve building a sync module
> of some sort, but i have no idea how that might be done.  Any prior art, or
> ideas about this?
>
>
>
> On Wednesday, April 29, 2020 at 7:00:25 PM UTC+1, Arlen Beiler wrote:
>>
>> Sorry, what I said was for tiddly server. What mark said is for tiddly
>> wiki.
>>
>> On Wed, Apr 29, 2020, 13:56 'Mark S.' via TiddlyWiki <
>> tiddl...@googlegroups.com> wrote:
>>
>>>
>>> The listen command can take a port number. Like
>>>
>>> --listen port=8090
>>>
>>>
>>> On Wednesday, April 29, 2020 at 9:37:36 AM UTC-7, ludwa6 wrote:
>>>>
>>>> Hey Arlen: Great to hear, thanks!
>>>> So i ran those commands, installed TiddlyServer on my Raspberry Pi
>>>> gateway... But hit a little snag setting up the listener, in that port
>>>> :8080 is owned by another application server.  Can't change that for the
>>>> moment, as it's a service i can't really mess with.  Could talk to that
>>>> developer about changing the port he's using, i suppose...
>>>>
>>>> But just to see this working, i tried to install on my Mac, but
>>>> terminal tells me:
>>>>
>>>> -bash: npm: command not found
>>>> Suppose i could use a different package manager, if i knew how (yes, i
>>>> am a complete unix n00b  =8-(
>>>>
>>>> Will try to bone up on the requisite skills, but any more crib notes
>>>> would of course be appreciated!
>>>>
>>>> /walt
>>>>
>>>>
>>>> On Wednesday, April 29, 2020 at 3:06:52 PM UTC+1, Arlen Beiler wrote:
>>>>>
>>>>> I have tried doing SQLite but there are some caveats that need to be
>>>>> accounted for.
>>>>>
>>>>> What I would recommend you do is use data folders instead of single
>>>>> file wikis. Data folders store tiddlers in individual text files using a
>>>>> custom format that Jeremy came up with. It works very well for text based
>>>>> storage solutions like GitHub. I'm actually really surprised no one
>>>>> mentioned this yet.
>>>>>
>>>>> To get started, install tiddlywiki globally by running npm install
>>>>> tiddlywiki -g
>>>>>
>>>>> Next, to create a blank data folder, run tiddlywiki ./MyNewWikiFolder
>>>>> --init server
>>>>>
>>>>> Then run tiddlywiki ./MyNewWikiFolder --listen
>

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

2020-04-29 Thread Arlen Beiler
Sorry, what I said was for tiddly server. What mark said is for tiddly wiki.

On Wed, Apr 29, 2020, 13:56 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

>
> The listen command can take a port number. Like
>
> --listen port=8090
>
>
> On Wednesday, April 29, 2020 at 9:37:36 AM UTC-7, ludwa6 wrote:
>>
>> Hey Arlen: Great to hear, thanks!
>> So i ran those commands, installed TiddlyServer on my Raspberry Pi
>> gateway... But hit a little snag setting up the listener, in that port
>> :8080 is owned by another application server.  Can't change that for the
>> moment, as it's a service i can't really mess with.  Could talk to that
>> developer about changing the port he's using, i suppose...
>>
>> But just to see this working, i tried to install on my Mac, but terminal
>> tells me:
>>
>> -bash: npm: command not found
>> Suppose i could use a different package manager, if i knew how (yes, i am
>> a complete unix n00b  =8-(
>>
>> Will try to bone up on the requisite skills, but any more crib notes
>> would of course be appreciated!
>>
>> /walt
>>
>>
>> On Wednesday, April 29, 2020 at 3:06:52 PM UTC+1, Arlen Beiler wrote:
>>>
>>> I have tried doing SQLite but there are some caveats that need to be
>>> accounted for.
>>>
>>> What I would recommend you do is use data folders instead of single file
>>> wikis. Data folders store tiddlers in individual text files using a custom
>>> format that Jeremy came up with. It works very well for text based storage
>>> solutions like GitHub. I'm actually really surprised no one mentioned this
>>> yet.
>>>
>>> To get started, install tiddlywiki globally by running npm install
>>> tiddlywiki -g
>>>
>>> Next, to create a blank data folder, run tiddlywiki ./MyNewWikiFolder
>>> --init server
>>>
>>> Then run tiddlywiki ./MyNewWikiFolder --listen
>>>
>>> Now open your browser to localhost:8080 and start exploring.
>>>
>>> TiddlyServer is a good way to load multiple data folders on the same
>>> port.
>>>
>>> Hope that helps,
>>> Arlen
>>>
>>> On Wed, Apr 29, 2020 at 7:52 AM ludwa6  wrote:
>>>
>>>> Such a wealth of options for Local-First storage have emerged in this
>>>> thread (must say: i'm super impressed with the strength of this community i
>>>> have just joined), i've been able to quickly implement the simple approach
>>>> suggested by Jeremy (TW Desktop, + cloud sync to Github), which is serving
>>>> me well enough for now.
>>>>
>>>> Yet, as i'm fast creating quite a mountain of data in TW, i'm also
>>>> bothered by the growing sense that what i really want at the back end of
>>>> this beautiful thing is a database -ideally SQLite, which has all that
>>>> local-first/ single-file/ portability goodness of TW, while bringing the
>>>> full set of functionalities needed to manage a large database with
>>>> integrity.  With a single SQLite file stored locally and replicated to the
>>>> cloud, that gives us a solution that ticks all the boxes in that
>>>> seminal Local-First paper
>>>> <https://www.inkandswitch.com/local-first.html>: Fast, Multi-Device,
>>>> Offline, Collaboration, Longevity, Privacy, User-Control.  Combining this
>>>> with the power of TW5 interface (really an "interface builder for the rest
>>>> of us," i would call it), minus mess of .html backup files i've got to keep
>>>> cleaning off my machine (SQLite has a full transactional history, so no
>>>> need of any backups but that one file, replicated to cloud), and that in
>>>> broad-strokes would be the shape of my dream machine.
>>>>
>>>> So i must ask: has anyone tried using SQLite as storage for a
>>>> TiddlyWiki?  If this is indeed technically feasible, can anyone point me to
>>>> prior art on which i might be able to build such a solution?  Though i am
>>>> no programmer, i am reasonably comfortable with SQL as a data manipulation
>>>> language, if someone can just show me how to get the TW data in there!
>>>>
>>>> --
>>>> 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 tiddl...@googlegroups.com.
>>>> To view this dis

Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

2020-04-29 Thread Arlen Beiler
I'm not at my computer right now, but you can specify the port in the
config file.

{ "bindInfo":{port:8090}}

On Wed, Apr 29, 2020, 12:37 ludwa6  wrote:

> Hey Arlen: Great to hear, thanks!
> So i ran those commands, installed TiddlyServer on my Raspberry Pi
> gateway... But hit a little snag setting up the listener, in that port
> :8080 is owned by another application server.  Can't change that for the
> moment, as it's a service i can't really mess with.  Could talk to that
> developer about changing the port he's using, i suppose...
>
> But just to see this working, i tried to install on my Mac, but terminal
> tells me:
>
> -bash: npm: command not found
> Suppose i could use a different package manager, if i knew how (yes, i am
> a complete unix n00b  =8-(
>
> Will try to bone up on the requisite skills, but any more crib notes would
> of course be appreciated!
>
> /walt
>
>
> On Wednesday, April 29, 2020 at 3:06:52 PM UTC+1, Arlen Beiler wrote:
>>
>> I have tried doing SQLite but there are some caveats that need to be
>> accounted for.
>>
>> What I would recommend you do is use data folders instead of single file
>> wikis. Data folders store tiddlers in individual text files using a custom
>> format that Jeremy came up with. It works very well for text based storage
>> solutions like GitHub. I'm actually really surprised no one mentioned this
>> yet.
>>
>> To get started, install tiddlywiki globally by running npm install
>> tiddlywiki -g
>>
>> Next, to create a blank data folder, run tiddlywiki ./MyNewWikiFolder
>> --init server
>>
>> Then run tiddlywiki ./MyNewWikiFolder --listen
>>
>> Now open your browser to localhost:8080 and start exploring.
>>
>> TiddlyServer is a good way to load multiple data folders on the same
>> port.
>>
>> Hope that helps,
>> Arlen
>>
>> On Wed, Apr 29, 2020 at 7:52 AM ludwa6  wrote:
>>
>>> Such a wealth of options for Local-First storage have emerged in this
>>> thread (must say: i'm super impressed with the strength of this community i
>>> have just joined), i've been able to quickly implement the simple approach
>>> suggested by Jeremy (TW Desktop, + cloud sync to Github), which is serving
>>> me well enough for now.
>>>
>>> Yet, as i'm fast creating quite a mountain of data in TW, i'm also
>>> bothered by the growing sense that what i really want at the back end of
>>> this beautiful thing is a database -ideally SQLite, which has all that
>>> local-first/ single-file/ portability goodness of TW, while bringing the
>>> full set of functionalities needed to manage a large database with
>>> integrity.  With a single SQLite file stored locally and replicated to the
>>> cloud, that gives us a solution that ticks all the boxes in that
>>> seminal Local-First paper
>>> <https://www.inkandswitch.com/local-first.html>: Fast, Multi-Device,
>>> Offline, Collaboration, Longevity, Privacy, User-Control.  Combining this
>>> with the power of TW5 interface (really an "interface builder for the rest
>>> of us," i would call it), minus mess of .html backup files i've got to keep
>>> cleaning off my machine (SQLite has a full transactional history, so no
>>> need of any backups but that one file, replicated to cloud), and that in
>>> broad-strokes would be the shape of my dream machine.
>>>
>>> So i must ask: has anyone tried using SQLite as storage for a
>>> TiddlyWiki?  If this is indeed technically feasible, can anyone point me to
>>> prior art on which i might be able to build such a solution?  Though i am
>>> no programmer, i am reasonably comfortable with SQL as a data manipulation
>>> language, if someone can just show me how to get the TW data in there!
>>>
>>> --
>>> 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 tiddl...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/856ad777-dc63-4491-bd74-c0391c4bf413%40googlegroups.com
>>> <https://groups.google.com/d/msgid/tiddlywiki/856ad777-dc63-4491-bd74-c0391c4bf413%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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

Re: [tw5] TiddlyWiki API/IFTTT help

2020-04-29 Thread Arlen Beiler
I don't exactly know how IFTTT works, but I think the best way would be to
push the content to your Dropbox or somewhere like that and then whenever
you open up your wiki you could press the button to import all of the
recent stuff from your Dropbox or wherever you have it stored, and it would
then be saved in your wiki using whatever saver method you normally use.

On Wed, Apr 29, 2020, 04:06 Tom  wrote:

> Hi All
> Just got started on using Tiddlywiki and have started to make it super
> useful for my personal usage.
> I am looking to make it a note-taking hub for everything and with that in
> mind I am looking to move away from my IFTTTs of importing information from
> Alexa lists, starred emails and spotify favourites into the likes of
> Evernote/OneNote/Excel but instead importing the information into
> TiddlyWiki (Tiddlywiki being the That part of IFTTT).
> I have also been using Beeminder to keep me on track with work such as
> daily note taking and journalling with entries to an excel updating the
> beeminder program (Tiddlywiki would the the This of IFTTT).
> If anyone can tell me how to use tiddly with IFTTT or the API in super
> simple terms it would be appreciated.
> If I need to elaborate further let me know.
> Many Thanks
> Tom
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/0890db3e-17c9-4e7d-b99d-46506c46a284%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTOJehpVRSeHXaQSsJLHkyziOz5BwA%2B324WTHPVOCb64A%40mail.gmail.com.


[tw5] Re: Question for TiddlyServer users

2020-04-29 Thread Arlen Beiler
Well, it seems like no one really cares what happens to logging. It never
was consistent anyway, since the data folder output still went to the
console only. I think I'll just say if anyone runs into serious problems
here feel free to open an issue on GitHub or email me here. Feel free to
post if you didn't notice this thread before this.

Arlen

On Tue, Apr 28, 2020 at 10:51 AM Arlen Beiler  wrote:

> Good morning everyone,
>
> As you may have noticed TiddlyServer 2.2 is now in the works, and the main
> goals are making it simpler and easier to use. So my question is who all
> uses the "logging" settings to log directly to a file. I'm planning to
> remove this to keep things simpler. The recommended way to handle long
> running processes is a process manager. I use PM2 on servers, and on
> desktop I never log to file, so I'm curious if anyone would really miss
> this feature if I removed it.
>
> I'm planning to print error messages to stderr and the startup messages
> and regular access logs to stdout, instead of writing them to files, so you
> can use redirection or other Node features to direct those streams to a
> file. If this is a seriously missed feature I can add a couple ways to do
> it but it seems like a rather complicated and niche feature, so I doubt
> anyone uses it.
>
> Just thought I'd ask
> Arlen
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQKMf%2BjPr5MDwkDwxNJgQZJe%3DHhvKRo5UM0c51Grxigqw%40mail.gmail.com.


Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

2020-04-29 Thread Arlen Beiler
I believe Tony is referring to the fact that a browser session is quickly
lost, including the unsaved data, once the user switches to a different app
on mobile devices. The only workaround that I know of would be to store
unsaved changes in local storage until they get synced. Which is basically
what noteself did.

So many different pieces of the puzzle. I often wish I could put them
together.

On Wed, Apr 29, 2020 at 9:03 AM Jed Carty  wrote:

> ludwa6,
>
> There have been a few database-backends made for tiddlywiki, I don't
> remember if anyone made a sqlite one or not, but it wouldn't be too hard
> and there are some examples around for it. I considered it for bob but I
> don't like sqlite, so I didn't use it.
>
> Tony,
>
> There is some misunderstanding here somewhere. I am completely lost. What
> is 'such a bob wiki' in this context? It acts like any other html wiki in
> the browser, it just has a plugin. I don't know what is new here or how
> being treated the same by the browser as an html wiki is something special.
>
> What works with the single file bob saver?
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/3f477a13-6892-491c-9498-21e54ce68e2f%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSRSL3hcahds0cz_3p%2BWmkUTRaWkQJuxWizrU3PjD9azww%40mail.gmail.com.


Re: [tw5] Re: Local-First Storage, with backup to cloud (Github)

2020-04-29 Thread Arlen Beiler
I have tried doing SQLite but there are some caveats that need to be
accounted for.

What I would recommend you do is use data folders instead of single file
wikis. Data folders store tiddlers in individual text files using a custom
format that Jeremy came up with. It works very well for text based storage
solutions like GitHub. I'm actually really surprised no one mentioned this
yet.

To get started, install tiddlywiki globally by running npm install
tiddlywiki -g

Next, to create a blank data folder, run tiddlywiki ./MyNewWikiFolder
--init server

Then run tiddlywiki ./MyNewWikiFolder --listen

Now open your browser to localhost:8080 and start exploring.

TiddlyServer is a good way to load multiple data folders on the same port.

Hope that helps,
Arlen

On Wed, Apr 29, 2020 at 7:52 AM ludwa6  wrote:

> Such a wealth of options for Local-First storage have emerged in this
> thread (must say: i'm super impressed with the strength of this community i
> have just joined), i've been able to quickly implement the simple approach
> suggested by Jeremy (TW Desktop, + cloud sync to Github), which is serving
> me well enough for now.
>
> Yet, as i'm fast creating quite a mountain of data in TW, i'm also
> bothered by the growing sense that what i really want at the back end of
> this beautiful thing is a database -ideally SQLite, which has all that
> local-first/ single-file/ portability goodness of TW, while bringing the
> full set of functionalities needed to manage a large database with
> integrity.  With a single SQLite file stored locally and replicated to the
> cloud, that gives us a solution that ticks all the boxes in that seminal
> Local-First paper : Fast,
> Multi-Device, Offline, Collaboration, Longevity, Privacy, User-Control.
> Combining this with the power of TW5 interface (really an "interface
> builder for the rest of us," i would call it), minus mess of .html backup
> files i've got to keep cleaning off my machine (SQLite has a full
> transactional history, so no need of any backups but that one file,
> replicated to cloud), and that in broad-strokes would be the shape of my
> dream machine.
>
> So i must ask: has anyone tried using SQLite as storage for a TiddlyWiki?
> If this is indeed technically feasible, can anyone point me to prior art on
> which i might be able to build such a solution?  Though i am no programmer,
> i am reasonably comfortable with SQL as a data manipulation language, if
> someone can just show me how to get the TW data in there!
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/856ad777-dc63-4491-bd74-c0391c4bf413%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdST-_8Lp6Q9TDGwKGG0NXw7JT9xbAKwm0ANOAzpMOSbcJQ%40mail.gmail.com.


Re: [tw5] Re: [meta] TiddlyWiki and... China - !?

2020-04-28 Thread Arlen Beiler
And Google is blocked in china...

On Tue, Apr 28, 2020 at 3:34 PM TiddlyTweeter 
wrote:

> Thomas Elmiger wrote:
>>
>>
>> Mark S.:
>>>
>>> But why is Switzerland #2?
>>>
>>
>> Is Google Trends considering population size? Then it was me, sorry!
>> ;–)
>>
>
> Thomas, have you been cloning? :-)
>
> [image: Annotation 2020-04-28 213038.jpg]
>
>
> Josiah, x
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/04a075fe-f614-478e-86c5-6ca0ae08f96a%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSR_qBspSCHrC8St6FwK8j53jAG9wYc9MahZp%3DFd6_fArg%40mail.gmail.com.


Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-04-28 Thread Arlen Beiler
>
> Minor comment: it is better to use the full path for index.js
>

Interesting. Where did you run into this? I'm curious because it would seem
preferable to have a relative path for portable installs, although if you
don't need to specify a drive letter on windows, it should work on at least
windows and macos mostly consistently. Perhaps specifying the __dirname
equivelant in bash would be another idea.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSR-qdF_NM_D3zBj%2BgbwL5-SBhy5PAj9wSP9BW%2Bhw9ZtAw%40mail.gmail.com.


Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-04-28 Thread Arlen Beiler
After doing it myself, I just realized that it is going to be way easier to
use NPM to create the portable install.


   - Create a new folder and cd into the folder.
   - Run "npm install tiddlyserver". Notice there is no -g option there.
   - Create your bash or batch file with the command
  - "node node_modules/tiddlyserver/index.js --config settings.json"
   - You can also download the Node executable and put in in the directory.
   If using bash, you need to add ./ (dot slash) to the beginning of the
   command.

That's it! Easy! There are some more changes coming to the NPM dependencies
that TiddlyServer uses so this option makes it easy to update as well. Just
run "npm install tiddlyserver@latest" on any computer that has NPM
installed on it, and you're updated. TiddlyServer specifies the exact
TiddlyWiki version so updating TiddlyServer will update the TiddlyWiki
dependencies as well.


On Tue, Apr 28, 2020 at 11:35 AM Mohammad Rahmani <
mohammad.rahm...@gmail.com> wrote:

> Arlen
>  I tested on Windows 10. It works fine!
>  Just one issue, It cannot create the backups folder and requires to have
> that folder in advance!
>
> Assume you have a working Node.js on your machine, follow this setup:
>
> 1. download tiddlyserver-2.2.0-alpha-3.zip and unzip in a separate folder
> 2. download tiddlywiki-production-5.1.22.zip and unzip in a separate
> folder
> 3. unzipping both in separate folders, both creates *package* folder
> 4. create a folder called TiddlyServer and put the content of package
> folder from step 1
> 5. create folder node_modulus in TiddlyServer folder
> 6. create folder tiddlywiki-production under  node_modulus
> 7. copy and paste the content of package folder from step 2 in
> tiddlywiki-production
> 8. create a setting.json as described in
> https://github.com/Arlen22/TiddlyServer/
> <https://github.com/Arlen22/TiddlyServer/releases/tag/v2.2.0-alpha-3>
> 9. open terminal
> 10. run:  node index.js --config settings.json
>
> That is all!
>
> [image: Slide-42.png]
>
>
>
> NOTE: You can put your *settings.json* everywhere you like and create a
> batch file to run TiddlyServer
> example
>
> *startServer.cmd*
> *node d:\TiddlyServer\index.js c:\mySandbox\settings.hson*
>
>
> Best wishes
> Mohammad
>
>
> On Tue, Apr 28, 2020 at 7:05 PM Arlen Beiler  wrote:
>
>> Here is the folder structure. Hopefully this helps. Let me know if you
>> have any further questions.
>>
>> TiddlyServer (you can rename this whatever you like)
>> This is the package folder from tiddlyserver-*
>> TiddlyServer/node_modules
>>  This is a folder you create
>> TiddlyServer/node_modules/tiddlywiki-production
>>  This is the package folder from tiddlywiki-production-*
>> TiddlyServer/index.js
>>  This is the executable bundle, run "node index.js"
>>
>> Arlen
>>
>> On Tue, Apr 28, 2020 at 2:54 AM Scott Kingery 
>> wrote:
>>
>>> Hi Arlen,
>>> I have Tiddlyserver working on a previous version and decided to do a
>>> fresh install. I like making it portable so I tried to do that again this
>>> time. Installing without NPM is a little wonky right now.
>>>
>>> I went here: https://github.com/Arlen22/TiddlyServer/releases/latest
>>> And grabbed:
>>> TiddlyServer-2.2.0-alpha-3.zip
>>> tiddlywiki-production-5.1.22.zip
>>>
>>> unzipped TiddlyServer-2.2.0-alpha-3.zip into a folder called twserver
>>> unzipped tiddlywiki-production-5.1.22.zip
>>>
>>> I believe I am supposed to rename the "package" folder that is in
>>> tiddlywiki-production-5.1.22.zip
>>> It is unclear to me whether package should be renamed tiddlywiki and
>>> simply put into my twserver folder OR if I should first create a folder
>>> called node_modules in twserver, rename package to tiddlywiki-production
>>> and put it into node_modules.
>>>
>>> Either way, your source currently does not have a server.js file nor can
>>> I find an index.js file.
>>>
>>> I decided to go the npm route because I have it available as well and
>>> was able to get things working with my old setting.json file. Things look
>>> pretty good with one exception. Unless I missed something, your plugins are
>>> still v5.1.21.
>>>
>>> Thanks for building this.
>>> Scott
>>>
>>>
>>>
>>> On Sunday, April 26, 2020 at 2:07:16 PM UTC-7, Arlen Beiler wrote:
>>>>
>>>> I apologize. The upgrade from 2.0 to 2.1 was quite significant. Here is
>>>> my getting 

Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-04-28 Thread Arlen Beiler
There are various changes under the hood, and I assume NodeJS is improving
as well, so possibly. Using a separate XML file for the tree is a feature
that I plan to implement but I have not yet. I just thought the semantics
of XML would be less confusing than JSON. You can currently specify a
separate JS or JSON file for the tree (which does need to have the correct
extension, lol).

On Tue, Apr 28, 2020 at 2:48 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

>
>
> On Tuesday, April 28, 2020 at 11:39:17 AM UTC-7, Arlen Beiler wrote:
>>
>> I'm very sure that was a typo, but I left it since that was how Mohammad
>> wrote it. In any case, TiddlyServer doesn't care what the extension is, it
>> expects a JSON file.
>>
>
>
> In your directions (unless they were changed) you mention that you can use
> an xml file. There is (or was) even a small snippet that used XML. But
> there were no directions that I could find that told how to invoke an xml
> file. Is the XML still in there, and if so, how is it invoked?
>
> I swap off between different saving techniques so that I can understand
> what other people are experiencing. So it's been awhile since I last used
> tiddlyserver. I feel that this time it is a little faster than before. Is
> that possible? Or a false memory? ;-)
>
> Thanks!
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/411051a3-f850-457b-baed-dc3e2f89f0c1%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/411051a3-f850-457b-baed-dc3e2f89f0c1%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQaBKY5%3DmuBGu-z661jWboKezsdNbiZtNAHNSCE5S9Tiw%40mail.gmail.com.


Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-04-28 Thread Arlen Beiler
I'm very sure that was a typo, but I left it since that was how Mohammad
wrote it. In any case, TiddlyServer doesn't care what the extension is, it
expects a JSON file.

On Tue, Apr 28, 2020 at 2:37 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> What is a hson file?
>
> On Tuesday, April 28, 2020 at 11:03:26 AM UTC-7, Arlen Beiler wrote:
>>
>> It should be *node d:\TiddlyServer\index.js --config
>> c:\mySandbox\settings.hson*
>>
>> On Tue, Apr 28, 2020 at 11:35 AM Mohammad Rahmani wrote:
>>
>>> Arlen
>>>  I tested on Windows 10. It works fine!
>>>  Just one issue, It cannot create the backups folder and requires to
>>> have that folder in advance!
>>>
>>> Assume you have a working Node.js on your machine, follow this setup:
>>>
>>> 1. download tiddlyserver-2.2.0-alpha-3.zip and unzip in a separate folder
>>> 2. download tiddlywiki-production-5.1.22.zip and unzip in a separate
>>> folder
>>> 3. unzipping both in separate folders, both creates *package* folder
>>> 4. create a folder called TiddlyServer and put the content of package
>>> folder from step 1
>>> 5. create folder node_modulus in TiddlyServer folder
>>> 6. create folder tiddlywiki-production under  node_modulus
>>> 7. copy and paste the content of package folder from step 2 in
>>> tiddlywiki-production
>>> 8. create a setting.json as described in
>>> https://github.com/Arlen22/TiddlyServer/
>>> <https://github.com/Arlen22/TiddlyServer/releases/tag/v2.2.0-alpha-3>
>>> 9. open terminal
>>> 10. run:  node index.js --config settings.json
>>>
>>> That is all!
>>>
>>> [image: Slide-42.png]
>>>
>>>
>>>
>>> NOTE: You can put your *settings.json* everywhere you like and create a
>>> batch file to run TiddlyServer
>>> example
>>>
>>> *startServer.cmd*
>>> *node d:\TiddlyServer\index.js c:\mySandbox\settings.hson*
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/41176131-ce88-4e90-82fc-71840d096436%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/41176131-ce88-4e90-82fc-71840d096436%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdST5wUqXhDgnKSUkXtZUvJOf-qhW1gXZCgvRpgPc6dCrKw%40mail.gmail.com.


Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-04-28 Thread Arlen Beiler
It should be *node d:\TiddlyServer\index.js --config
c:\mySandbox\settings.hson*

On Tue, Apr 28, 2020 at 11:35 AM Mohammad Rahmani <
mohammad.rahm...@gmail.com> wrote:

> Arlen
>  I tested on Windows 10. It works fine!
>  Just one issue, It cannot create the backups folder and requires to have
> that folder in advance!
>
> Assume you have a working Node.js on your machine, follow this setup:
>
> 1. download tiddlyserver-2.2.0-alpha-3.zip and unzip in a separate folder
> 2. download tiddlywiki-production-5.1.22.zip and unzip in a separate
> folder
> 3. unzipping both in separate folders, both creates *package* folder
> 4. create a folder called TiddlyServer and put the content of package
> folder from step 1
> 5. create folder node_modulus in TiddlyServer folder
> 6. create folder tiddlywiki-production under  node_modulus
> 7. copy and paste the content of package folder from step 2 in
> tiddlywiki-production
> 8. create a setting.json as described in
> https://github.com/Arlen22/TiddlyServer/
> <https://github.com/Arlen22/TiddlyServer/releases/tag/v2.2.0-alpha-3>
> 9. open terminal
> 10. run:  node index.js --config settings.json
>
> That is all!
>
> [image: Slide-42.png]
>
>
>
> NOTE: You can put your *settings.json* everywhere you like and create a
> batch file to run TiddlyServer
> example
>
> *startServer.cmd*
> *node d:\TiddlyServer\index.js c:\mySandbox\settings.hson*
>
>
> Best wishes
> Mohammad
>
>
> On Tue, Apr 28, 2020 at 7:05 PM Arlen Beiler  wrote:
>
>> Here is the folder structure. Hopefully this helps. Let me know if you
>> have any further questions.
>>
>> TiddlyServer (you can rename this whatever you like)
>> This is the package folder from tiddlyserver-*
>> TiddlyServer/node_modules
>>  This is a folder you create
>> TiddlyServer/node_modules/tiddlywiki-production
>>  This is the package folder from tiddlywiki-production-*
>> TiddlyServer/index.js
>>  This is the executable bundle, run "node index.js"
>>
>> Arlen
>>
>> On Tue, Apr 28, 2020 at 2:54 AM Scott Kingery 
>> wrote:
>>
>>> Hi Arlen,
>>> I have Tiddlyserver working on a previous version and decided to do a
>>> fresh install. I like making it portable so I tried to do that again this
>>> time. Installing without NPM is a little wonky right now.
>>>
>>> I went here: https://github.com/Arlen22/TiddlyServer/releases/latest
>>> And grabbed:
>>> TiddlyServer-2.2.0-alpha-3.zip
>>> tiddlywiki-production-5.1.22.zip
>>>
>>> unzipped TiddlyServer-2.2.0-alpha-3.zip into a folder called twserver
>>> unzipped tiddlywiki-production-5.1.22.zip
>>>
>>> I believe I am supposed to rename the "package" folder that is in
>>> tiddlywiki-production-5.1.22.zip
>>> It is unclear to me whether package should be renamed tiddlywiki and
>>> simply put into my twserver folder OR if I should first create a folder
>>> called node_modules in twserver, rename package to tiddlywiki-production
>>> and put it into node_modules.
>>>
>>> Either way, your source currently does not have a server.js file nor can
>>> I find an index.js file.
>>>
>>> I decided to go the npm route because I have it available as well and
>>> was able to get things working with my old setting.json file. Things look
>>> pretty good with one exception. Unless I missed something, your plugins are
>>> still v5.1.21.
>>>
>>> Thanks for building this.
>>> Scott
>>>
>>>
>>>
>>> On Sunday, April 26, 2020 at 2:07:16 PM UTC-7, Arlen Beiler wrote:
>>>>
>>>> I apologize. The upgrade from 2.0 to 2.1 was quite significant. Here is
>>>> my getting started guide for 2.1 and up.
>>>> https://arlen22.github.io/tiddlyserver/docs/gettingstarted
>>>>
>>>> You can just copy the tree property over, but the other settings are
>>>> different for the most part.
>>>>
>>>> Arlen
>>>>
>>>> On Sun, Apr 26, 2020 at 4:02 PM 'Mark S.' via TiddlyWiki <
>>>> tiddl...@googlegroups.com> wrote:
>>>>
>>>>> The startup didn't like my old 2.0 settings file. The upgrade
>>>>> instructions
>>>>> say to use example-settings.json file as a starting point. But there
>>>>> are only
>>>>> two json files in the directories (package.json), and neither are
>>>>> example-settings.json.
>>>>>
&g

[tw5] Question for TiddlyServer users

2020-04-28 Thread Arlen Beiler
Good morning everyone,

As you may have noticed TiddlyServer 2.2 is now in the works, and the main
goals are making it simpler and easier to use. So my question is who all
uses the "logging" settings to log directly to a file. I'm planning to
remove this to keep things simpler. The recommended way to handle long
running processes is a process manager. I use PM2 on servers, and on
desktop I never log to file, so I'm curious if anyone would really miss
this feature if I removed it.

I'm planning to print error messages to stderr and the startup messages and
regular access logs to stdout, instead of writing them to files, so you can
use redirection or other Node features to direct those streams to a file.
If this is a seriously missed feature I can add a couple ways to do it but
it seems like a rather complicated and niche feature, so I doubt anyone
uses it.

Just thought I'd ask
Arlen

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQEJRDHTmxbLr8QY_bMz1D8cOQH-Zn2GFLatScVbtgWkQ%40mail.gmail.com.


Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-04-28 Thread Arlen Beiler
Here is the folder structure. Hopefully this helps. Let me know if you have
any further questions.

TiddlyServer (you can rename this whatever you like)
This is the package folder from tiddlyserver-*
TiddlyServer/node_modules
 This is a folder you create
TiddlyServer/node_modules/tiddlywiki-production
 This is the package folder from tiddlywiki-production-*
TiddlyServer/index.js
 This is the executable bundle, run "node index.js"

Arlen

On Tue, Apr 28, 2020 at 2:54 AM Scott Kingery 
wrote:

> Hi Arlen,
> I have Tiddlyserver working on a previous version and decided to do a
> fresh install. I like making it portable so I tried to do that again this
> time. Installing without NPM is a little wonky right now.
>
> I went here: https://github.com/Arlen22/TiddlyServer/releases/latest
> And grabbed:
> TiddlyServer-2.2.0-alpha-3.zip
> tiddlywiki-production-5.1.22.zip
>
> unzipped TiddlyServer-2.2.0-alpha-3.zip into a folder called twserver
> unzipped tiddlywiki-production-5.1.22.zip
>
> I believe I am supposed to rename the "package" folder that is in
> tiddlywiki-production-5.1.22.zip
> It is unclear to me whether package should be renamed tiddlywiki and
> simply put into my twserver folder OR if I should first create a folder
> called node_modules in twserver, rename package to tiddlywiki-production
> and put it into node_modules.
>
> Either way, your source currently does not have a server.js file nor can I
> find an index.js file.
>
> I decided to go the npm route because I have it available as well and was
> able to get things working with my old setting.json file. Things look
> pretty good with one exception. Unless I missed something, your plugins are
> still v5.1.21.
>
> Thanks for building this.
> Scott
>
>
>
> On Sunday, April 26, 2020 at 2:07:16 PM UTC-7, Arlen Beiler wrote:
>>
>> I apologize. The upgrade from 2.0 to 2.1 was quite significant. Here is
>> my getting started guide for 2.1 and up.
>> https://arlen22.github.io/tiddlyserver/docs/gettingstarted
>>
>> You can just copy the tree property over, but the other settings are
>> different for the most part.
>>
>> Arlen
>>
>> On Sun, Apr 26, 2020 at 4:02 PM 'Mark S.' via TiddlyWiki <
>> tiddl...@googlegroups.com> wrote:
>>
>>> The startup didn't like my old 2.0 settings file. The upgrade
>>> instructions
>>> say to use example-settings.json file as a starting point. But there are
>>> only
>>> two json files in the directories (package.json), and neither are
>>> example-settings.json.
>>>
>>> On Sunday, April 26, 2020 at 6:00:02 AM UTC-7, Arlen Beiler wrote:
>>>>
>>>> To run it portable, use "node index.js" instead of the "tiddlyserver"
>>>> command.  (sorry, forgot to mention the name change).
>>>>
>>>> tiddlyserver-* contains a package folder which should be renamed
>>>> TiddlyServer.
>>>>
>>>> tiddlywiki-production-* contains a package folder which should become
>>>> TiddlyServer/node_modules/tiddlywiki-production. In other words, create the
>>>> node_modules folder, and put the tiddlywiki-production package folder
>>>> inside that and rename it tiddlywiki-production.
>>>>
>>>> TiddlyServer
>>>> This is the package folder from tiddlyserver-*
>>>> TiddlyServer/node_modules
>>>>  This is a folder you create
>>>> TiddlyServer/node_modules/tiddlywiki-production
>>>>  This is the package folder from tiddlywiki-production-*
>>>> TiddlyServer/index.js
>>>>  This is the executable bundle, run "node index.js"
>>>>
>>>> Hope that helps. Let me know if it is still unclear.
>>>>
>>>> I do appreciate you all's feedback, thanks,
>>>> Arlen
>>>>
>>>> On Sat, Apr 25, 2020 at 11:14 PM 'Mark S.' via TiddlyWiki <
>>>> tiddl...@googlegroups.com> wrote:
>>>>
>>>>> I'm running Linux, but like Mohammad I don't see a server.js file in
>>>>> the unzipped packages.
>>>>>
>>>>> On Friday, April 24, 2020 at 1:39:44 PM UTC-7, Arlen Beiler wrote:
>>>>>>
>>>>>> Hello Everyone,
>>>>>>
>>>>> --
>>>>> 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 tiddl...@go

Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-04-26 Thread Arlen Beiler
I apologize. The upgrade from 2.0 to 2.1 was quite significant. Here is my
getting started guide for 2.1 and up.
https://arlen22.github.io/tiddlyserver/docs/gettingstarted

You can just copy the tree property over, but the other settings are
different for the most part.

Arlen

On Sun, Apr 26, 2020 at 4:02 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> The startup didn't like my old 2.0 settings file. The upgrade instructions
> say to use example-settings.json file as a starting point. But there are
> only
> two json files in the directories (package.json), and neither are
> example-settings.json.
>
> On Sunday, April 26, 2020 at 6:00:02 AM UTC-7, Arlen Beiler wrote:
>>
>> To run it portable, use "node index.js" instead of the "tiddlyserver"
>> command.  (sorry, forgot to mention the name change).
>>
>> tiddlyserver-* contains a package folder which should be renamed
>> TiddlyServer.
>>
>> tiddlywiki-production-* contains a package folder which should become
>> TiddlyServer/node_modules/tiddlywiki-production. In other words, create the
>> node_modules folder, and put the tiddlywiki-production package folder
>> inside that and rename it tiddlywiki-production.
>>
>> TiddlyServer
>> This is the package folder from tiddlyserver-*
>> TiddlyServer/node_modules
>>  This is a folder you create
>> TiddlyServer/node_modules/tiddlywiki-production
>>  This is the package folder from tiddlywiki-production-*
>> TiddlyServer/index.js
>>  This is the executable bundle, run "node index.js"
>>
>> Hope that helps. Let me know if it is still unclear.
>>
>> I do appreciate you all's feedback, thanks,
>> Arlen
>>
>> On Sat, Apr 25, 2020 at 11:14 PM 'Mark S.' via TiddlyWiki <
>> tiddlywiki@googlegroups.com> wrote:
>>
>>> I'm running Linux, but like Mohammad I don't see a server.js file in the
>>> unzipped packages.
>>>
>>> On Friday, April 24, 2020 at 1:39:44 PM UTC-7, Arlen Beiler wrote:
>>>>
>>>> Hello Everyone,
>>>>
>>> --
>>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/4b1ff989-9762-4cfd-bb35-7e9b87d718e3%40googlegroups.com
>>> <https://groups.google.com/d/msgid/tiddlywiki/4b1ff989-9762-4cfd-bb35-7e9b87d718e3%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/24d7d2fb-b0d0-44e5-8379-2f4e8f86d611%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/24d7d2fb-b0d0-44e5-8379-2f4e8f86d611%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQqeBxobPXfmP%2Bdu2cm37xRbgo9dKAwbYwD5Sneo25_Kg%40mail.gmail.com.


Re: [tw5] Re: TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-04-26 Thread Arlen Beiler
To run it portable, use "node index.js" instead of the "tiddlyserver"
command.  (sorry, forgot to mention the name change).

tiddlyserver-* contains a package folder which should be renamed
TiddlyServer.

tiddlywiki-production-* contains a package folder which should become
TiddlyServer/node_modules/tiddlywiki-production. In other words, create the
node_modules folder, and put the tiddlywiki-production package folder
inside that and rename it tiddlywiki-production.

TiddlyServer
This is the package folder from tiddlyserver-*
TiddlyServer/node_modules
 This is a folder you create
TiddlyServer/node_modules/tiddlywiki-production
 This is the package folder from tiddlywiki-production-*
TiddlyServer/index.js
 This is the executable bundle, run "node index.js"

Hope that helps. Let me know if it is still unclear.

I do appreciate you all's feedback, thanks,
Arlen

On Sat, Apr 25, 2020 at 11:14 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> I'm running Linux, but like Mohammad I don't see a server.js file in the
> unzipped packages.
>
> On Friday, April 24, 2020 at 1:39:44 PM UTC-7, Arlen Beiler wrote:
>>
>> Hello Everyone,
>>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/4b1ff989-9762-4cfd-bb35-7e9b87d718e3%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/4b1ff989-9762-4cfd-bb35-7e9b87d718e3%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSfLVpyfeP7L9fcTx3Riyofz68PYR1sKo9L8a37X5Epfw%40mail.gmail.com.


Re: [tw5] TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-04-24 Thread Arlen Beiler
Yes. It is used for data folders and also the entire folder is served at
/assets/tiddlywiki/. None of the regular TiddlyServer stuff applies to it
(like permissions, file saving, loading data folders), it just serves the
requested file if it exists.

On Fri, Apr 24, 2020 at 4:59 PM Saq Imtiaz  wrote:

> Can I use my own copy of the TiddlyWiki code by setting this appropriately?
>
> "_datafoldertarget":"/path/to/tiddlywiki"
>
> Thanks,
> Saq
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/42faaabd-136e-4ff4-9919-25a6ab7864a0%40googlegroups.com
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSRiQBLVRSz4MCjL5EP9pk%3Drcyn_VUp_-50VcWC3uW9ATg%40mail.gmail.com.


[tw5] TiddlyServer upgraded to 5.1.22 (and NPM install)

2020-04-24 Thread Arlen Beiler
Hello Everyone,

I've upgraded TiddlyServer to target 5.1.22.

@someguynamedmatt helped rearrange the build process, resulting in a clean
production build. So, I've now published TiddlyServer to npm and you can
install it by running

 npm install -g tiddlyserver

This will install it globally, which also puts it in your PATH, so you can
run it directly using

 tiddlyserver --config /path/to/settings.json

Windows should also work just fine. You can use the tilde (~) if your shell
supports it. I forgot to include tilde support for the config parameter (if
the shell passes it through). I'll add that in the future.

If you don't have npm installed or you want to do a portable install,
you'll find the archives listed at
https://github.com/Arlen22/TiddlyServer/releases/tag/v2.2.0-alpha-3. I
downloaded the tgz files from npm, and the zip files are the same archive
converted to a zip file.

I've separated out the tiddlywiki bundle into a separate npm package. If
you're familiar with that it's still the same idea. I will add more info to
the readme, but for now it's ready to use. It also includes the client-side
.js files for adding in an html page, which probably nobody uses yet. I'm
still working on the use cases and so forth for that, so that's just a
little teaser.

https://www.npmjs.com/package/tiddlywiki-production

As always, remember to create backups before upgrading.

Enjoy,
Arlen

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQ26P-vG44Bt_GJ-NsytudYM15JR5VTpD_n1TndmPR-7Q%40mail.gmail.com.


Re: [tw5] Re: Possible TiddlyServer, node or Bob Feature idea

2020-04-23 Thread Arlen Beiler
In order to get the server route to work properly, you should need to add
exports.bodyFormat === "stream"

On Thu, Apr 23, 2020 at 7:01 PM Saq Imtiaz  wrote:

> Jed, looks like I was on the right track but this will save me a fair bit
> of work.
> For anyone else interested these are the relevant files from Bob:
>
> Server route:
> https://github.com/OokTech/TW5-Bob/blob/master/ServerRoutes/post-upload.js
> Client side hook:
> https://github.com/OokTech/TW5-ServerImages/blob/master/ServerImages.js
>
> On Friday, April 24, 2020 at 12:51:18 AM UTC+2, Saq Imtiaz wrote:
>>
>> Jed: thank you!! I'll have a look at the Bob source code.
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/da84b4e1-7aec-4ebf-9310-22a4b8f67ad3%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSS%2BJskdpYavyS-JgS3r%2Bwnr%3DEE7S4jkirOYrBFpvAv%2BYQ%40mail.gmail.com.


Re: [tw5] Re: Possible TiddlyServer, node or Bob Feature idea

2020-04-23 Thread Arlen Beiler
The functionality is already built into TiddlyServer, and it's a standard
HTML Form from a folder's directory index. However, all requests relating
to data folders are handled by the TiddlyWiki server functions for that
data folder, so anything that relates to the files directory or anything
else inside a data folder will need to be handled by the TiddlyWiki server
directly. I would be glad to make sure this functionality works with
TiddlyServer as well, and would also like to get this into the core or a
core plugin. Please keep us updated as to your progress on this. I am very
keen to see how this turns out.

Hope it helps,
Arlen

On Thu, Apr 23, 2020 at 7:01 PM Saq Imtiaz  wrote:

> Jed, looks like I was on the right track but this will save me a fair bit
> of work.
> For anyone else interested these are the relevant files from Bob:
>
> Server route:
> https://github.com/OokTech/TW5-Bob/blob/master/ServerRoutes/post-upload.js
> Client side hook:
> https://github.com/OokTech/TW5-ServerImages/blob/master/ServerImages.js
>
> On Friday, April 24, 2020 at 12:51:18 AM UTC+2, Saq Imtiaz wrote:
>>
>> Jed: thank you!! I'll have a look at the Bob source code.
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/da84b4e1-7aec-4ebf-9310-22a4b8f67ad3%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSRhE8wJ%3DnrKcux_tYjrpVcBEJFssSHWr9LA_EeZoF636g%40mail.gmail.com.


Re: [tw5] Re: A Portable Tiddlywiki Node.Js on a Thumb Drive

2020-04-20 Thread Arlen Beiler
Interesting. My comments are based on my knowledge of TiddlyWiki and having
written TiddlyServer myself. I've never audited NodeJS to find out what
files it would write to. I'll have to do that sometime. By the way, here's
a good tool that I use to check what programs are doing on Windows. It's
what I would use for a thorough audit.

Process Explorer - Windows Sysinternals | Microsoft Docs
<https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer>


On Mon, Apr 20, 2020 at 1:59 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> My actual testing in the past indicates that directories get created down
> in the roaming data directories, whether you're using node.js or
> tiddlydesktop or tiddlyserver. What it "should" do is another issue. It
> would be interesting to know what happens if someone attempts to run on a
> secure computer. I suppose there's only a handful of people who will care
> about some obscure directory being written to, but it's a good thing to
> keep in mind.
>
> On Monday, April 20, 2020 at 10:30:23 AM UTC-7, Arlen Beiler wrote:
>>
>> The node executable itself should never write to disk, unless instructed
>> to do so with the fs module, and I'm not aware of any operations that write
>> to a temp directory either.
>>
>> The npm installation is separate and definitely scatters files in quite a
>> few places, although this can be restricted using npm settings.
>>
>> TiddlyServer may write to a temp directory if you upload files (it uses
>> the formidable library) but then it moves the file to the correct directory
>> using the rename command, so it would only be left there if the upload
>> fails part way thorough. Other than that, TiddlyServer never writes to any
>> directory not specified in settings.json (whether that's a tree path,
>> backup directory, or log file). It does write to a file called
>> uncaughtException.log if there is an uncaught exception, which is always in
>> the installation directory.
>>
>> I am not aware that Node TiddlyWiki writes to anywhere outside of the
>> data folder. But it would depend on which plugins are loaded. Each plugin
>> has its own characteristics, but for the most part, it should not write
>> anywhere outside the data folder. That should be true of all the stock
>> plugins.
>>
>> Hope that helps.
>>
>> On Mon, Apr 20, 2020 at 11:34 AM 'Mark S.' via TiddlyWiki <
>> tiddlywiki@googlegroups.com> wrote:
>>
>>>
>>> I don't know about portable node.js, but I'm reasonably sure that
>>> node.js lifted from a zip deployment will leave crumbs in the operating
>>> system's directories. The thing I wonder is, if you tried this on a secure
>>> machine, whether it would send up some alarm because the disk is being
>>> written to.
>>>
>>> Since the idea of a portable tiddlywiki is to not leave any traces, this
>>> is an important consideration.
>>>
>>> On Friday, April 17, 2020 at 1:53:32 PM UTC-7, Arlen Beiler wrote:
>>>>
>>>> Another way is to download the zip file from NodeJS.org, and copy the
>>>> node.exe file into the tiddlywiki folder, then (on windows) run "node.exe
>>>> tiddlywiki.js". You can download the tiddlywiki folder from GitHub. It
>>>> sounds like that is slightly more complicated than your method, but just
>>>> thought I'd mention it.
>>>>
>>>> On Fri, Apr 17, 2020 at 4:01 PM 'Mark S.' via TiddlyWiki <
>>>> tiddlywiki@googlegroups.com> wrote:
>>>>
>>>>> If you use "-g", isn't it putting the data down in your user drive? Or
>>>>> is it smart enough to put it all on the thumb drive ?
>>>>>
>>>>> Plus, in the past, node had a habit of creating empty directories in
>>>>> the app/roaming directories even if you had specified specific local
>>>>> directories. This would be hard to detect unless you test on a machine 
>>>>> that
>>>>> has never used node.js at all. That is, is it possible that bread crumbs
>>>>> are being left even if you use a portable device?
>>>>>
>>>>>
>>>>> On Friday, April 17, 2020 at 12:41:12 PM UTC-7, Mohammad wrote:
>>>>>>
>>>>>> You may like to have a Tiddlywiki on Node.js with all its features on
>>>>>> a thumb drive!
>>>>>> Or a Plug and Play Tiddlywiki.
>>>>>>
>>>>>> If so, this is a short instruction for Windows user.
>>>>>&

Re: [tw5] Re: Local host address server tip

2020-04-20 Thread Arlen Beiler
I might have said that last part wrong. The docs should have it correct.

On Mon, Apr 20, 2020 at 1:37 PM Arlen Beiler  wrote:

> TiddlyServer allows you to specify a range of IP addresses to listen on.
>
> There is more information here:
> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#section-bindinfo
>
> You might need to experiment a little with different options. BindWildcard
> only binds to 0.0.0.0 and then filters requests as they come in (if
> filterBindAddress is also set).
>
> On Wed, Apr 1, 2020 at 8:14 PM TonyM  wrote:
>
>> Mario
>>
>> Or is that Paranoia Mario? ;), I am glad you are reviewing it.
>>
>> My above solution is Actualy simple and effective. All I do is set the
>> server local address to a 127.0.4.8x address. Rather than using 0.0.0.0 to
>> host on the lan I use 192.168.1.8x for each server (currently additional ip
>> addresses on my laptop) and it is only accessible on the lan when I am on
>> the 192.168.1.x network, and my own computer can always access them at the
>> local host addresses.
>>
>> But I look forward to finding new methods.
>>
>> Regards
>> Tony
>>
>> --
>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/80822280-1a08-41e9-9e16-8a6a88f3b834%40googlegroups.com
>> .
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSR6kW1hD3sTU%3Dou9A%2B-EbypdYJxC2ehW8NhGbuo4dCJ7Q%40mail.gmail.com.


Re: [tw5] Re: Local host address server tip

2020-04-20 Thread Arlen Beiler
TiddlyServer allows you to specify a range of IP addresses to listen on.

There is more information here:
https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#section-bindinfo

You might need to experiment a little with different options. BindWildcard
only binds to 0.0.0.0 and then filters requests as they come in (if
filterBindAddress is also set).

On Wed, Apr 1, 2020 at 8:14 PM TonyM  wrote:

> Mario
>
> Or is that Paranoia Mario? ;), I am glad you are reviewing it.
>
> My above solution is Actualy simple and effective. All I do is set the
> server local address to a 127.0.4.8x address. Rather than using 0.0.0.0 to
> host on the lan I use 192.168.1.8x for each server (currently additional ip
> addresses on my laptop) and it is only accessible on the lan when I am on
> the 192.168.1.x network, and my own computer can always access them at the
> local host addresses.
>
> But I look forward to finding new methods.
>
> Regards
> Tony
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/80822280-1a08-41e9-9e16-8a6a88f3b834%40googlegroups.com
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSxdPjMqu9en7MxHCt40w%2BFbmEDTEgvaX67Q7Wp72B7Uw%40mail.gmail.com.


Re: [tw5] Re: A Portable Tiddlywiki Node.Js on a Thumb Drive

2020-04-20 Thread Arlen Beiler
The node executable itself should never write to disk, unless instructed to
do so with the fs module, and I'm not aware of any operations that write to
a temp directory either.

The npm installation is separate and definitely scatters files in quite a
few places, although this can be restricted using npm settings.

TiddlyServer may write to a temp directory if you upload files (it uses the
formidable library) but then it moves the file to the correct directory
using the rename command, so it would only be left there if the upload
fails part way thorough. Other than that, TiddlyServer never writes to any
directory not specified in settings.json (whether that's a tree path,
backup directory, or log file). It does write to a file called
uncaughtException.log if there is an uncaught exception, which is always in
the installation directory.

I am not aware that Node TiddlyWiki writes to anywhere outside of the data
folder. But it would depend on which plugins are loaded. Each plugin has
its own characteristics, but for the most part, it should not write
anywhere outside the data folder. That should be true of all the stock
plugins.

Hope that helps.

On Mon, Apr 20, 2020 at 11:34 AM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

>
> I don't know about portable node.js, but I'm reasonably sure that node.js
> lifted from a zip deployment will leave crumbs in the operating system's
> directories. The thing I wonder is, if you tried this on a secure machine,
> whether it would send up some alarm because the disk is being written to.
>
> Since the idea of a portable tiddlywiki is to not leave any traces, this
> is an important consideration.
>
> On Friday, April 17, 2020 at 1:53:32 PM UTC-7, Arlen Beiler wrote:
>>
>> Another way is to download the zip file from NodeJS.org, and copy the
>> node.exe file into the tiddlywiki folder, then (on windows) run "node.exe
>> tiddlywiki.js". You can download the tiddlywiki folder from GitHub. It
>> sounds like that is slightly more complicated than your method, but just
>> thought I'd mention it.
>>
>> On Fri, Apr 17, 2020 at 4:01 PM 'Mark S.' via TiddlyWiki <
>> tiddlywiki@googlegroups.com> wrote:
>>
>>> If you use "-g", isn't it putting the data down in your user drive? Or
>>> is it smart enough to put it all on the thumb drive ?
>>>
>>> Plus, in the past, node had a habit of creating empty directories in the
>>> app/roaming directories even if you had specified specific local
>>> directories. This would be hard to detect unless you test on a machine that
>>> has never used node.js at all. That is, is it possible that bread crumbs
>>> are being left even if you use a portable device?
>>>
>>>
>>> On Friday, April 17, 2020 at 12:41:12 PM UTC-7, Mohammad wrote:
>>>>
>>>> You may like to have a Tiddlywiki on Node.js with all its features on a
>>>> thumb drive!
>>>> Or a Plug and Play Tiddlywiki.
>>>>
>>>> If so, this is a short instruction for Windows user.
>>>>
>>>> 1. Download the portable Node.js:  (NodeJSPortable_6.14.2.zip)  from
>>>> here
>>>>   https://github.com/garethflowers/nodejs-portable/releases
>>>>
>>>> 2. Unzip on your thumb drive in the folder of choice
>>>>
>>>> 3. Run NodeJSPortable.exe
>>>>
>>>> 4. In the command window appears install Tiddlywiki with below command
>>>> (you need internet access)
>>>> npm install -g tiddlywiki
>>>>
>>>> 5. That's all
>>>>
>>>>
>>>> Make a test
>>>> 1. Create a new wiki, by entering  below command
>>>> tiddlywiki mynewwiki --init server
>>>>
>>>> 2. Run your wiki by entering  below command
>>>> tiddlywiki mynewwiki --listen
>>>>
>>>> 3. Open a browser (FF, Chrome, Edge, Safari, ...) and
>>>>  visit http://127.0.0.1:8080/ in your browser
>>>>
>>>>
>>>> It has all the same features as Tiddlywiki on NodeJS, plus, it leaves
>>>> no personal information behind on the machine you run it on, so you can
>>>> take it with you wherever you go.
>>>>
>>>>
>>>> This is another journey in Tiddlywiki wonderland.
>>>>
>>>> --Mohammad
>>>>
>>>>
>>>> --
>>> 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
>>> 

Re: [tw5] Re: A Portable Tiddlywiki Node.Js on a Thumb Drive

2020-04-20 Thread Arlen Beiler
In this test, was the wiki a single-file wiki or a data folder? And I'm
assuming from the way you wrote it that you were running TiddlyServer, not
Node TiddlyWiki (which would be a datafolder), right?

On Sun, Apr 19, 2020 at 1:09 PM Mohammad  wrote:

> Arlen,
> I did some tests! I see around 40-55MB when node is idle and around
> 86-92MB when it is active (e.g TW is opened in browser and one edits it)
>
> [image: pic-33.png]
> So, node seems hungry and eats memory!
>
> Amazingly TWexe assume 4MB per wiki and Apache when is used 33MB (16 + 18)
> but none have the feature you have on node.js
> The Twexe and Apache serve single .html
>
> Just for information
>
> --Mohammad
>
>
>
> On Sunday, April 19, 2020 at 6:24:21 PM UTC+4:30, Arlen Beiler wrote:
>>
>> Ok, I ran top to see what the memory actually is. My computer is a 16 GB
>> machine. TiddlyWiki on Node uses 150 MB. TiddlyServer used 100 MB per wiki
>> (approximately), but less than 30 MB when no wikis were loaded (sorry, top
>> only listed the first page of results). Now, given Node's memory
>> management, I would guess that a more constrained environment would use
>> less, so I'm curious what results other people get.
>>
>> In my mind, this is huge, so I'm not surprised people need a way around
>> it, but I'm not sure what the culprit is. I'll do some digging. All I know
>> is it's it's big on Node TiddlyWiki and on TiddlyServer both, so it's
>> probably somewhere in TiddlyWiki.
>>
>> On Sun, Apr 19, 2020 at 8:47 AM Arlen Beiler  wrote:
>>
>>> People have in the past had problems with memory consumption when using
>>> data folders and because TiddlyServer is intended to load data folders as
>>> faithfully as possible, Jed created Bob, which does things a little
>>> different but still works with almost all data folders. However the latest
>>> raspberry pi should have enough memory to be able to handle TiddlyServer
>>> quite easily. I’m assuming one would get the 4 GB version if you’re going
>>> to use it for a server anyway. So I’m guessing this isn’t as big of a
>>> problem as it used to be.
>>>
>>> Single file wikis on the other hand shouldn’t take much memory. The
>>> TiddlyServer  documentation says how to enable back ups for single file
>>> wikis. And the WebDAV saver works as expected, unlike Apache.
>>>
>>> On Sun, Apr 19, 2020 at 04:16 Mohammad  wrote:
>>>
>>>> Further to the instruction by Arlen one can download simplesrv
>>>>
>>>> https://github.com/lucsan/simpserv
>>>>
>>>>
>>>> and create a readonly webserver to fire any single .html Tiddlywiki.
>>>>
>>>> So, it possible to have a portable webserver for Tiddlywiki (and
>>>> holding plugin libraries) on a thumb drive
>>>> The size of server 14MB if one use Node.JS 6.x
>>>>
>>>> In summary
>>>>
>>>> 1. Follow the instruction by Arlen above, lets you have a tiny
>>>> NodeJS+Tiddlywiki server (read/write/save) + (Arlen may guide us to create
>>>> backup)
>>>> 2. Add the simpleserv above to have a readonly webserver on another port
>>>> 3. Put all in folder on a thumb drive
>>>>
>>>> The above setup is small and can be used on Raspberry Pi and similar
>>>> device.
>>>>
>>>> I am thinking  one can put whole of these on an old Android cell phone
>>>> and setup a portable NodeJS+Tiddlywiki server
>>>>
>>>>
>>>>
>>>> On Saturday, April 18, 2020 at 1:23:32 AM UTC+4:30, Arlen Beiler wrote:
>>>>>
>>>>> Another way is to download the zip file from NodeJS.org, and copy the
>>>>> node.exe file into the tiddlywiki folder, then (on windows) run "node.exe
>>>>> tiddlywiki.js". You can download the tiddlywiki folder from GitHub. It
>>>>> sounds like that is slightly more complicated than your method, but just
>>>>> thought I'd mention it.
>>>>>
>>>>> On Fri, Apr 17, 2020 at 4:01 PM 'Mark S.' via TiddlyWiki <
>>>>> tiddl...@googlegroups.com> wrote:
>>>>>
>>>> If you use "-g", isn't it putting the data down in your user drive? Or
>>>>>> is it smart enough to put it all on the thumb drive ?
>>>>>>
>>>>>> Plus, in the past, node had a habit of creating empty directories in
>>>>>> the app/roaming directories even if you had specified specific local

Re: [tw5] Re: A Portable Tiddlywiki Node.Js on a Thumb Drive

2020-04-20 Thread Arlen Beiler
Node TiddlyWiki (which handles data folders) is responsible for the large
memory consumption. As best as I can tell it's actually not something
TiddlyServer can do anything about. Single file wikis on TiddlyServer
should have similar memory consumption to the other products you mentioned
that serve single file wikis.

On Sun, Apr 19, 2020 at 1:09 PM Mohammad  wrote:

> Arlen,
> I did some tests! I see around 40-55MB when node is idle and around
> 86-92MB when it is active (e.g TW is opened in browser and one edits it)
>
> [image: pic-33.png]
> So, node seems hungry and eats memory!
>
> Amazingly TWexe assume 4MB per wiki and Apache when is used 33MB (16 + 18)
> but none have the feature you have on node.js
> The Twexe and Apache serve single .html
>
> Just for information
>
> --Mohammad
>
>
>
> On Sunday, April 19, 2020 at 6:24:21 PM UTC+4:30, Arlen Beiler wrote:
>>
>> Ok, I ran top to see what the memory actually is. My computer is a 16 GB
>> machine. TiddlyWiki on Node uses 150 MB. TiddlyServer used 100 MB per wiki
>> (approximately), but less than 30 MB when no wikis were loaded (sorry, top
>> only listed the first page of results). Now, given Node's memory
>> management, I would guess that a more constrained environment would use
>> less, so I'm curious what results other people get.
>>
>> In my mind, this is huge, so I'm not surprised people need a way around
>> it, but I'm not sure what the culprit is. I'll do some digging. All I know
>> is it's it's big on Node TiddlyWiki and on TiddlyServer both, so it's
>> probably somewhere in TiddlyWiki.
>>
>> On Sun, Apr 19, 2020 at 8:47 AM Arlen Beiler  wrote:
>>
>>> People have in the past had problems with memory consumption when using
>>> data folders and because TiddlyServer is intended to load data folders as
>>> faithfully as possible, Jed created Bob, which does things a little
>>> different but still works with almost all data folders. However the latest
>>> raspberry pi should have enough memory to be able to handle TiddlyServer
>>> quite easily. I’m assuming one would get the 4 GB version if you’re going
>>> to use it for a server anyway. So I’m guessing this isn’t as big of a
>>> problem as it used to be.
>>>
>>> Single file wikis on the other hand shouldn’t take much memory. The
>>> TiddlyServer  documentation says how to enable back ups for single file
>>> wikis. And the WebDAV saver works as expected, unlike Apache.
>>>
>>> On Sun, Apr 19, 2020 at 04:16 Mohammad  wrote:
>>>
>>>> Further to the instruction by Arlen one can download simplesrv
>>>>
>>>> https://github.com/lucsan/simpserv
>>>>
>>>>
>>>> and create a readonly webserver to fire any single .html Tiddlywiki.
>>>>
>>>> So, it possible to have a portable webserver for Tiddlywiki (and
>>>> holding plugin libraries) on a thumb drive
>>>> The size of server 14MB if one use Node.JS 6.x
>>>>
>>>> In summary
>>>>
>>>> 1. Follow the instruction by Arlen above, lets you have a tiny
>>>> NodeJS+Tiddlywiki server (read/write/save) + (Arlen may guide us to create
>>>> backup)
>>>> 2. Add the simpleserv above to have a readonly webserver on another port
>>>> 3. Put all in folder on a thumb drive
>>>>
>>>> The above setup is small and can be used on Raspberry Pi and similar
>>>> device.
>>>>
>>>> I am thinking  one can put whole of these on an old Android cell phone
>>>> and setup a portable NodeJS+Tiddlywiki server
>>>>
>>>>
>>>>
>>>> On Saturday, April 18, 2020 at 1:23:32 AM UTC+4:30, Arlen Beiler wrote:
>>>>>
>>>>> Another way is to download the zip file from NodeJS.org, and copy the
>>>>> node.exe file into the tiddlywiki folder, then (on windows) run "node.exe
>>>>> tiddlywiki.js". You can download the tiddlywiki folder from GitHub. It
>>>>> sounds like that is slightly more complicated than your method, but just
>>>>> thought I'd mention it.
>>>>>
>>>>> On Fri, Apr 17, 2020 at 4:01 PM 'Mark S.' via TiddlyWiki <
>>>>> tiddl...@googlegroups.com> wrote:
>>>>>
>>>> If you use "-g", isn't it putting the data down in your user drive? Or
>>>>>> is it smart enough to put it all on the thumb drive ?
>>>>>>
>>>>>> Plus, in the past, node had a habit of cre

Re: [tw5] Re: A Portable Tiddlywiki Node.Js on a Thumb Drive

2020-04-19 Thread Arlen Beiler
Ok, I ran top to see what the memory actually is. My computer is a 16 GB
machine. TiddlyWiki on Node uses 150 MB. TiddlyServer used 100 MB per wiki
(approximately), but less than 30 MB when no wikis were loaded (sorry, top
only listed the first page of results). Now, given Node's memory
management, I would guess that a more constrained environment would use
less, so I'm curious what results other people get.

In my mind, this is huge, so I'm not surprised people need a way around it,
but I'm not sure what the culprit is. I'll do some digging. All I know is
it's it's big on Node TiddlyWiki and on TiddlyServer both, so it's probably
somewhere in TiddlyWiki.

On Sun, Apr 19, 2020 at 8:47 AM Arlen Beiler  wrote:

> People have in the past had problems with memory consumption when using
> data folders and because TiddlyServer is intended to load data folders as
> faithfully as possible, Jed created Bob, which does things a little
> different but still works with almost all data folders. However the latest
> raspberry pi should have enough memory to be able to handle TiddlyServer
> quite easily. I’m assuming one would get the 4 GB version if you’re going
> to use it for a server anyway. So I’m guessing this isn’t as big of a
> problem as it used to be.
>
> Single file wikis on the other hand shouldn’t take much memory. The
> TiddlyServer  documentation says how to enable back ups for single file
> wikis. And the WebDAV saver works as expected, unlike Apache.
>
> On Sun, Apr 19, 2020 at 04:16 Mohammad  wrote:
>
>> Further to the instruction by Arlen one can download simplesrv
>>
>> https://github.com/lucsan/simpserv
>>
>>
>> and create a readonly webserver to fire any single .html Tiddlywiki.
>>
>> So, it possible to have a portable webserver for Tiddlywiki (and holding
>> plugin libraries) on a thumb drive
>> The size of server 14MB if one use Node.JS 6.x
>>
>> In summary
>>
>> 1. Follow the instruction by Arlen above, lets you have a tiny
>> NodeJS+Tiddlywiki server (read/write/save) + (Arlen may guide us to create
>> backup)
>> 2. Add the simpleserv above to have a readonly webserver on another port
>> 3. Put all in folder on a thumb drive
>>
>> The above setup is small and can be used on Raspberry Pi and similar
>> device.
>>
>> I am thinking  one can put whole of these on an old Android cell phone
>> and setup a portable NodeJS+Tiddlywiki server
>>
>>
>>
>> On Saturday, April 18, 2020 at 1:23:32 AM UTC+4:30, Arlen Beiler wrote:
>>>
>>> Another way is to download the zip file from NodeJS.org, and copy the
>>> node.exe file into the tiddlywiki folder, then (on windows) run "node.exe
>>> tiddlywiki.js". You can download the tiddlywiki folder from GitHub. It
>>> sounds like that is slightly more complicated than your method, but just
>>> thought I'd mention it.
>>>
>>> On Fri, Apr 17, 2020 at 4:01 PM 'Mark S.' via TiddlyWiki <
>>> tiddl...@googlegroups.com> wrote:
>>>
>> If you use "-g", isn't it putting the data down in your user drive? Or is
>>>> it smart enough to put it all on the thumb drive ?
>>>>
>>>> Plus, in the past, node had a habit of creating empty directories in
>>>> the app/roaming directories even if you had specified specific local
>>>> directories. This would be hard to detect unless you test on a machine that
>>>> has never used node.js at all. That is, is it possible that bread crumbs
>>>> are being left even if you use a portable device?
>>>>
>>>>
>>>> On Friday, April 17, 2020 at 12:41:12 PM UTC-7, Mohammad wrote:
>>>>>
>>>>> You may like to have a Tiddlywiki on Node.js with all its features on
>>>>> a thumb drive!
>>>>> Or a Plug and Play Tiddlywiki.
>>>>>
>>>>> If so, this is a short instruction for Windows user.
>>>>>
>>>>> 1. Download the portable Node.js:  (NodeJSPortable_6.14.2.zip)  from
>>>>> here
>>>>>   https://github.com/garethflowers/nodejs-portable/releases
>>>>>
>>>>> 2. Unzip on your thumb drive in the folder of choice
>>>>>
>>>>> 3. Run NodeJSPortable.exe
>>>>>
>>>>> 4. In the command window appears install Tiddlywiki with below command
>>>>> (you need internet access)
>>>>> npm install -g tiddlywiki
>>>>>
>>>>> 5. That's all
>>>>>
>>>>>
>>>>> Make a test
>>>>>

Re: [tw5] Re: A Portable Tiddlywiki Node.Js on a Thumb Drive

2020-04-19 Thread Arlen Beiler
People have in the past had problems with memory consumption when using
data folders and because TiddlyServer is intended to load data folders as
faithfully as possible, Jed created Bob, which does things a little
different but still works with almost all data folders. However the latest
raspberry pi should have enough memory to be able to handle TiddlyServer
quite easily. I’m assuming one would get the 4 GB version if you’re going
to use it for a server anyway. So I’m guessing this isn’t as big of a
problem as it used to be.

Single file wikis on the other hand shouldn’t take much memory. The
TiddlyServer  documentation says how to enable back ups for single file
wikis. And the WebDAV saver works as expected, unlike Apache.

On Sun, Apr 19, 2020 at 04:16 Mohammad  wrote:

> Further to the instruction by Arlen one can download simplesrv
>
> https://github.com/lucsan/simpserv
>
>
> and create a readonly webserver to fire any single .html Tiddlywiki.
>
> So, it possible to have a portable webserver for Tiddlywiki (and holding
> plugin libraries) on a thumb drive
> The size of server 14MB if one use Node.JS 6.x
>
> In summary
>
> 1. Follow the instruction by Arlen above, lets you have a tiny
> NodeJS+Tiddlywiki server (read/write/save) + (Arlen may guide us to create
> backup)
> 2. Add the simpleserv above to have a readonly webserver on another port
> 3. Put all in folder on a thumb drive
>
> The above setup is small and can be used on Raspberry Pi and similar
> device.
>
> I am thinking  one can put whole of these on an old Android cell phone and
> setup a portable NodeJS+Tiddlywiki server
>
>
>
> On Saturday, April 18, 2020 at 1:23:32 AM UTC+4:30, Arlen Beiler wrote:
>>
>> Another way is to download the zip file from NodeJS.org, and copy the
>> node.exe file into the tiddlywiki folder, then (on windows) run "node.exe
>> tiddlywiki.js". You can download the tiddlywiki folder from GitHub. It
>> sounds like that is slightly more complicated than your method, but just
>> thought I'd mention it.
>>
>> On Fri, Apr 17, 2020 at 4:01 PM 'Mark S.' via TiddlyWiki <
>> tiddl...@googlegroups.com> wrote:
>>
> If you use "-g", isn't it putting the data down in your user drive? Or is
>>> it smart enough to put it all on the thumb drive ?
>>>
>>> Plus, in the past, node had a habit of creating empty directories in the
>>> app/roaming directories even if you had specified specific local
>>> directories. This would be hard to detect unless you test on a machine that
>>> has never used node.js at all. That is, is it possible that bread crumbs
>>> are being left even if you use a portable device?
>>>
>>>
>>> On Friday, April 17, 2020 at 12:41:12 PM UTC-7, Mohammad wrote:
>>>>
>>>> You may like to have a Tiddlywiki on Node.js with all its features on a
>>>> thumb drive!
>>>> Or a Plug and Play Tiddlywiki.
>>>>
>>>> If so, this is a short instruction for Windows user.
>>>>
>>>> 1. Download the portable Node.js:  (NodeJSPortable_6.14.2.zip)  from
>>>> here
>>>>   https://github.com/garethflowers/nodejs-portable/releases
>>>>
>>>> 2. Unzip on your thumb drive in the folder of choice
>>>>
>>>> 3. Run NodeJSPortable.exe
>>>>
>>>> 4. In the command window appears install Tiddlywiki with below command
>>>> (you need internet access)
>>>> npm install -g tiddlywiki
>>>>
>>>> 5. That's all
>>>>
>>>>
>>>> Make a test
>>>> 1. Create a new wiki, by entering  below command
>>>> tiddlywiki mynewwiki --init server
>>>>
>>>> 2. Run your wiki by entering  below command
>>>> tiddlywiki mynewwiki --listen
>>>>
>>>> 3. Open a browser (FF, Chrome, Edge, Safari, ...) and
>>>>  visit http://127.0.0.1:8080/ in your browser
>>>>
>>>>
>>>> It has all the same features as Tiddlywiki on NodeJS, plus, it leaves
>>>> no personal information behind on the machine you run it on, so you can
>>>> take it with you wherever you go.
>>>>
>>>>
>>>> This is another journey in Tiddlywiki wonderland.
>>>>
>>>> --Mohammad
>>>>
>>>>
>>>> --
>>> 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
>>> ema

Re: [tw5] Possible TiddlyServer, node or Bob Feature idea

2020-04-18 Thread Arlen Beiler
TiddlyServer has this capability. You can upload files and create new
directories within directories. You can set the name when you upload it.
Currently, if the file exists it will be overwritten. If you cannot see the
upload button in the directory index, you are either on a group index
(meaning a branch of the tree (group), rather than a "leaf" (folder) so to
speak, or it you need to set the upload permission for either
localAddressPermission (i.e. the listening IP address) or for the logged in
user. The functionality is there but I haven't really documented it well
yet.

For TiddlyWiki on Node you would just need to create a plugin to upload to
the files directory. I don't think the functionality is built-in currently.
It would be great to have a proper upload manager that takes gives you
upload status and so forth. That should also work on TiddlyServer. I'd be
happy to test it to make sure. I wouldn't be surprised if a plugin already
exists but maybe I misunderstood the original intent of the files folder.



On Sat, Apr 18, 2020 at 12:57 AM TonyM  wrote:

> Jed, Arlen et all,
>
> As mentioned in passing here
>  Bob
> is now capable of serving files, as is TiddlyServer and Node static
> tiddlers but what about the reverse at least for a secure environment?
>
> For example a server based drop box, where files can be dropped into a
> files global or wiki local and further if tid or json import them? Here I
> am referring to a URL address rather than the local file system, however
> this should be possible as well.
>
> Regards
> Tony
>
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/9448f4ff-af2b-43da-be75-cef2265139fd%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTEcgbrYp3DrPS9bDPjXKaxibjQHHgw%2BDY29gLZ_0Ch1Q%40mail.gmail.com.


Re: [tw5] Re: A Portable Tiddlywiki Node.Js on a Thumb Drive

2020-04-17 Thread Arlen Beiler
Another way is to download the zip file from NodeJS.org, and copy the
node.exe file into the tiddlywiki folder, then (on windows) run "node.exe
tiddlywiki.js". You can download the tiddlywiki folder from GitHub. It
sounds like that is slightly more complicated than your method, but just
thought I'd mention it.

On Fri, Apr 17, 2020 at 4:01 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> If you use "-g", isn't it putting the data down in your user drive? Or is
> it smart enough to put it all on the thumb drive ?
>
> Plus, in the past, node had a habit of creating empty directories in the
> app/roaming directories even if you had specified specific local
> directories. This would be hard to detect unless you test on a machine that
> has never used node.js at all. That is, is it possible that bread crumbs
> are being left even if you use a portable device?
>
>
> On Friday, April 17, 2020 at 12:41:12 PM UTC-7, Mohammad wrote:
>>
>> You may like to have a Tiddlywiki on Node.js with all its features on a
>> thumb drive!
>> Or a Plug and Play Tiddlywiki.
>>
>> If so, this is a short instruction for Windows user.
>>
>> 1. Download the portable Node.js:  (NodeJSPortable_6.14.2.zip)  from here
>>   https://github.com/garethflowers/nodejs-portable/releases
>>
>> 2. Unzip on your thumb drive in the folder of choice
>>
>> 3. Run NodeJSPortable.exe
>>
>> 4. In the command window appears install Tiddlywiki with below command
>> (you need internet access)
>> npm install -g tiddlywiki
>>
>> 5. That's all
>>
>>
>> Make a test
>> 1. Create a new wiki, by entering  below command
>> tiddlywiki mynewwiki --init server
>>
>> 2. Run your wiki by entering  below command
>> tiddlywiki mynewwiki --listen
>>
>> 3. Open a browser (FF, Chrome, Edge, Safari, ...) and
>>  visit http://127.0.0.1:8080/ in your browser
>>
>>
>> It has all the same features as Tiddlywiki on NodeJS, plus, it leaves no
>> personal information behind on the machine you run it on, so you can take
>> it with you wherever you go.
>>
>>
>> This is another journey in Tiddlywiki wonderland.
>>
>> --Mohammad
>>
>>
>> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/9bc1ec76-a308-472c-b99c-f66e5dd31519%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTnfVopScafo4wk059MbG8YsW4n9oAeHOu3dOoQpJUktQ%40mail.gmail.com.


Re: [tw5] iOS Users, Rejoice! Quine 2 is here

2020-03-21 Thread Arlen Beiler
I think that still uses single-file wikis, in which case you're still
better off using Quine 2. Good to know about that option though, for other
related purposes!

On Sat, Mar 21, 2020 at 4:56 PM brianburnham  wrote:

> Diego,
>
> Not sure if this helps for your purposes, but I do know you can run/save
> tiddlywiki on iOS using phpwin (app) and store.php (PHP self hosting option
> on tiddlywiki.com).
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/2cd66338-7c48-4b65-8e11-429ecc174aaf%40googlegroups.com
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSRpQwgdFM06vYXOMPCP67PQ%3DjUN4Yt-n7j%3Dd0joKhcr6w%40mail.gmail.com.


Re: [tw5] Re: iOS Users, Rejoice! Quine 2 is here

2020-03-20 Thread Arlen Beiler
Correct. You'll have to find another solution for that.

On Fri, Mar 20, 2020 at 9:57 AM Diego Mesa  wrote:

> Arlen,
>
> To make sure I understand, if I use node.js TW and keep all of my .tid
> files on Dropbox. This app will *not* let me use TW on my ipad like that
> correct? We have to be in single-file mode with TW for this to work?
>
>
>
> On Thursday, March 19, 2020 at 9:12:26 PM UTC-5, Arlen Beiler wrote:
>>
>> In other words, in case I didn't make it clear, the FE File Explorer app
>> integrates with the Files app as a storage provider, which means that you
>> should be able to use Quine 2 to edit files over the 10+ protocols FE File
>> Explorer supports, just like you can edit your Dropbox files with Quine 2.
>> I didn't test it yet, but I think it should work that way.
>>
>> On Thu, Mar 19, 2020 at 10:06 PM Arlen Beiler  wrote:
>>
>>> Not to steal any thunder from Chris Hunt, but I think this deserves a
>>> cross post.
>>>
>>> Quine 2 is "Ready for Sale" and will appear in the App Store almost
>>> immediately.
>>>
>>> Sincere thanks to all of the beta testers - it's been so important to
>>> have their critical eyes on the App over the last couple of months. They've
>>> been a huge help.
>>>
>>> I hope Quine 2 doesn't disappoint. As mentioned previously, it has been
>>> my primary App on the iPad for over a year now at the same time as I've
>>> been refining it and moving over to iOS 13 for multi-window support.
>>>
>>> I am biased of course but for my purposes TiddlyWiki and now Quine 2 are
>>> what make the iPad into a productive platform for my needs - ESPECIALLY
>>> with multi-window support.
>>>
>>> Have fun,
>>>
>>> Chris.
>>>
>>> P.S. from Arlen:
>>>
>>> This app integrates with the iOS Files app allowing you to access files
>>> in cloud storage apps. This means you can edit your files in your Dropbox
>>> directly inside Quine 2 and the Dropbox app immediately saves your changes
>>> back to Dropbox. It looks like the Google Drive app also has this
>>> integration. I think any cloud storage worth their salt probably does.
>>>
>>> Another app which lets you integrate with many cloud storage providers,
>>> as well as network shares, is FE File Explorer Pro
>>> https://apps.apple.com/us/app/fe-file-explorer-pro/id499470113
>>>
>>> This is a great day to be an iOS user!
>>>
>>> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/0f68963c-435d-493a-a820-6608b185af3e%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/0f68963c-435d-493a-a820-6608b185af3e%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSF-askCs1o86_-TD4rKb4vFg-uucRggz27xTYLZurtQg%40mail.gmail.com.


[tw5] Re: iOS Users, Rejoice! Quine 2 is here

2020-03-19 Thread Arlen Beiler
In other words, in case I didn't make it clear, the FE File Explorer app
integrates with the Files app as a storage provider, which means that you
should be able to use Quine 2 to edit files over the 10+ protocols FE File
Explorer supports, just like you can edit your Dropbox files with Quine 2.
I didn't test it yet, but I think it should work that way.

On Thu, Mar 19, 2020 at 10:06 PM Arlen Beiler  wrote:

> Not to steal any thunder from Chris Hunt, but I think this deserves a
> cross post.
>
> Quine 2 is "Ready for Sale" and will appear in the App Store almost
> immediately.
>
> Sincere thanks to all of the beta testers - it's been so important to have
> their critical eyes on the App over the last couple of months. They've been
> a huge help.
>
> I hope Quine 2 doesn't disappoint. As mentioned previously, it has been my
> primary App on the iPad for over a year now at the same time as I've been
> refining it and moving over to iOS 13 for multi-window support.
>
> I am biased of course but for my purposes TiddlyWiki and now Quine 2 are
> what make the iPad into a productive platform for my needs - ESPECIALLY
> with multi-window support.
>
> Have fun,
>
> Chris.
>
> P.S. from Arlen:
>
> This app integrates with the iOS Files app allowing you to access files in
> cloud storage apps. This means you can edit your files in your Dropbox
> directly inside Quine 2 and the Dropbox app immediately saves your changes
> back to Dropbox. It looks like the Google Drive app also has this
> integration. I think any cloud storage worth their salt probably does.
>
> Another app which lets you integrate with many cloud storage providers, as
> well as network shares, is FE File Explorer Pro
> https://apps.apple.com/us/app/fe-file-explorer-pro/id499470113
>
> This is a great day to be an iOS user!
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSRu7AijHhe83zdPfJGbWJJfkxuuTi5g4xciz-Qixm_zyA%40mail.gmail.com.


[tw5] iOS Users, Rejoice! Quine 2 is here

2020-03-19 Thread Arlen Beiler
Not to steal any thunder from Chris Hunt, but I think this deserves a cross
post.

Quine 2 is "Ready for Sale" and will appear in the App Store almost
immediately.

Sincere thanks to all of the beta testers - it's been so important to have
their critical eyes on the App over the last couple of months. They've been
a huge help.

I hope Quine 2 doesn't disappoint. As mentioned previously, it has been my
primary App on the iPad for over a year now at the same time as I've been
refining it and moving over to iOS 13 for multi-window support.

I am biased of course but for my purposes TiddlyWiki and now Quine 2 are
what make the iPad into a productive platform for my needs - ESPECIALLY
with multi-window support.

Have fun,

Chris.

P.S. from Arlen:

This app integrates with the iOS Files app allowing you to access files in
cloud storage apps. This means you can edit your files in your Dropbox
directly inside Quine 2 and the Dropbox app immediately saves your changes
back to Dropbox. It looks like the Google Drive app also has this
integration. I think any cloud storage worth their salt probably does.

Another app which lets you integrate with many cloud storage providers, as
well as network shares, is FE File Explorer Pro
https://apps.apple.com/us/app/fe-file-explorer-pro/id499470113

This is a great day to be an iOS user!

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTa4YqX0kJ5Pwh-Za4hnS2RGRy%3DdF-t4QyHpxBzO10c-Q%40mail.gmail.com.


Re: [tw5] Re: Consider renaming TiddlyWiki

2020-03-12 Thread Arlen Beiler
LOL, I didn't mean to make it sound like it was headed toward PHP! I meant
it was headed toward being a stand-alone specification with an
implementation in Javascript, but which could be re-implemented in a
different language due to the wikitext characteristics. It still could be
but NodeJS is mature enough that another implementation will probably never
be needed. Good summary.

Arlen

On Thu, Mar 12, 2020 at 12:11 PM TiddlyTweeter 
wrote:

> Ciao Arlen
>
> This is one of the most interesting overviews I have ever read about TW!
>
> I redacted parts of it to foreground the main thrust.
>
> Many thanks!
>
> TT
>
> Arlen Beiler wrote:
>>
>> TiddlyWiki is not a multi-user platform. In fact, it is arguably not a
>> platform at all. It is actually a syntax.
>>
>
>
>> It is a specification, not a library.
>>
>
>
>> It can be implemented in any language.
>>
>
>
>> Jeremy has implemented it in a Javascript library ...
>>
>
>
>> It could just as easily be implemented in PHP as a server-side multi-user
>> CMS ...
>>
>
>
>> That was the original direction TiddlyWiki Five was headed.
>>
>
>
>> Popular demand has since been slowly pushing it toward some Javascript
>> dependencies, but it is still a specification.
>>
>
>
>> It just so happens that browsers make it really easy to implement
>> specifications that only involve one user editing a document at a time and
>> not needing to serve it across the network. The network optimizations came
>> much later in the form of TiddlyServer and Bob...
>>
>
>
>> Anyway, hope that gives some perspective on the possibilities of what we
>> have in our hands. From someone who has spent his TiddlyWiki time poking
>> around the Javascript implementation and trying to make it do stuff it
>> wanted to be able to do but never got around to doing. Ok,
>>
>
>
>> * I know that sounds funny, but in the early days there were a lot of
>> stubs in the code and it was obvious that certain things were intended to
>> be implemented but there was never a demand for it so it never happened. *
>>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/902ff950-c475-4967-936e-11cdce2e532a%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/902ff950-c475-4967-936e-11cdce2e532a%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSV-WSLNjmohqsfKMbD9rOgbn_Mp6cspHi8KDJj4oz7Vg%40mail.gmail.com.


Re: [tw5] Re: Consider renaming TiddlyWiki

2020-03-12 Thread Arlen Beiler
TiddlyWiki is not a multi-user platform. In fact, it is arguably not a
platform at all. It is actually a syntax. It is a specification, not a
library. It can be implemented in any language. Jeremy has implemented it
in a Javascript library (wikitext parser) and single-user document
framework (core widgets) in the browser. He decided to call them all
TiddlyWiki for confusion's sake (just kidding, it actually makes sense). It
could just as easily be implemented in PHP as a server-side multi-user CMS
(assuming you call several thousand hours of work easy). Sure, the UI might
be slightly different if implemented like that, but it would still be
TiddlyWiki.

That was the original direction TiddlyWiki Five was headed. Popular demand
has since been slowly pushing it toward some Javascript dependencies, but
it is still a specification. I haven't been innocent of that either, having
originally not comprehended the full scope of the project.

It just so happens that browsers make it really easy to implement
specifications that only involve one user editing a document at a time and
not needing to serve it across the network. The network optimizations came
much later in the form of TiddlyServer and Bob, as well as some
improvements in the core --listen command.

It definitely fits in with other wikis. The common feature of all wikis is
the ability to link between pages, and to easily create new pages, and
organize those pages using templates. I came from MediaWiki, and while the
framework isn't the same, the specification is very similar. The word
"wiki" puts it in a category that you can expect certain features from, and
while it isn't multi-user, it actually is very easy to have multiple people
edit it, especially with the Node version and a few tweaks. It isn't really
meant for WikiPedia, but then again WikiPedia has outgrown its own wikitext
many times over. I would have been thrilled to have some of the features of
TiddlyWiki syntax in MediaWiki back when I was an editor on WikiPedia.
That's why I switched to TiddlyWiki. Some things are just so much easier.

And nothing is harder, except MediaWiki allows you to transclude an open
tag without closing it and then close it later with a second template! In
tiddlywiki you have to put the whole thing in a macro and use a set widget
to get the header and footer then include them as substitutions. You can't
do it in the main part of the page. But that's a minor problem and has a
rather simple fix I thought of just now.

Anyway, hope that gives some perspective on the possibilities of what we
have in our hands. From someone who has spent his TiddlyWiki time poking
around the Javascript implementation and trying to make it do stuff it
wanted to be able to do but never got around to doing. Ok, I know that
sounds funny, but in the early days there were a lot of stubs in the code
and it was obvious that certain things were intended to be implemented but
there was never a demand for it so it never happened.

One of these days I'll write a multi-user plugin. Jeremy is working on an
update to make syncing more dependable which will make it a lot easier. And
the server has already been updated. One of these days, it's going to
happen.

Arlen

On Thu, Mar 12, 2020 at 7:21 AM David Gifford  wrote:

> https://images.app.goo.gl/ocbyB1U2xTK5wVb98
>
> On Thursday, March 12, 2020 at 2:39:40 AM UTC-6, Ste Wilson wrote:
>>
>> David wins! Orangutan for the win! Chimp was so last comment! :D
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/709f99e5-c084-4f88-98d3-865611268b70%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSRixULdJ220Dx%3DV8CQ8AO7AXqqDMQjZuJxvZDZ1wdqJew%40mail.gmail.com.


Re: [tw5] Re: Consider renaming TiddlyWiki

2020-03-09 Thread Arlen Beiler
Wiki is a category which refers to small, easy-to-setup, wall-of-text
content management systems, usually equipped with a simple default theme,
but infinitely customizable with enough tiem and patience.

On Mon, Mar 9, 2020 at 4:17 PM TiddlyTweeter 
wrote:

> Arlen, not a criticism, but what is the meaning here of "Wiki"? What does
> it add?
>
> My concern about it is its in a way empty of meaning.
>
> I think if you used a wiki it makes some sense. But if you haven't?
>
> Just gentle thoughts
> Josiah
>
> On Monday, 9 March 2020 21:07:52 UTC+1, Arlen Beiler wrote:
>>
>> AtomicWiki
>> That's another idea. I think it captures the essence of TiddlyWiki.
>>
>> Or the office suite :)
>> NoteWiki
>> SheetWiki
>> SlideWiki
>> TableWiki
>>
>> More ideas
>> PageWiki
>>
>> Coral Platform (the idea of living building blocks)
>>
>>
>>
>>
>> MinnoWiki seems to carry about as much appeal as TiddlyWiki (if you have
>> no negative connotation for the word "Tiddly"), I would think.
>>
>> Arlen
>>
>> On Mon, Mar 9, 2020 at 9:07 AM TiddlyTweeter  wrote:
>>
>>> My sense is that the real solution to TiddlyWiki gaining more traction
>>>> in the marketplace is about creating one or more compelling "killer apps"
>>>> that fill widely-perceived, but under-served demands for a particular set
>>>> of features rather than avoiding any general aversion to the underlying
>>>> TiddlyWiki name, and that changing the name will accomplish almost nothing
>>>> in this regard.
>>>
>>>
>>> Eric, am I allowed to agree with both you & Mark S. ? :-)
>>>
>>> The "killer apps" part of this I fully agree with. It simply makes sense
>>> to me to address niches with precise solutions, which is exactly what TW is
>>> spectacularly good at.
>>>
>>> And we may already have them but don't seem to have a way to advance
>>> them.
>>>
>>> So there is, maybe, a missing promo piece?
>>>
>>> Thoughts
>>> TT
>>>
>>> On Sunday, 8 March 2020 05:11:51 UTC+1, Eric Shulman wrote:
>>>>
>>>> On Saturday, March 7, 2020 at 5:05:36 PM UTC-8, Mark S. wrote:
>>>>>
>>>>> I think if we had stats, you'd find that basically there's about 350
>>>>> million people
>>>>>
>>>>
>>>> If we had stats... then we would have a number... but without stats,
>>>> saying "350 million" is just an imagined number.  This reminds of an old
>>>> saying: "86.3% of all statistics are made up on the spot" :)
>>>>
>>>>
>>>>> who will automatically discount a product that has a childish,
>>>>> non-serious, and embarrassing name like "Tiddly--anything".
>>>>>
>>>>
>>>> I think you are vastly overstating the "embarrassing" aspect.  I
>>>> suspect that is more of a personal response on your part, rather than some
>>>> general truth.  As I wrote previously:
>>>>
>>>> *REAL adults... evaluate the cost/benefit relationship to their
>>>> objectives, and adopt whatever tech makes sense to meet their goals.*
>>>>
>>>> Yes, there are PROMOTED products with childish names (e.g. Duck Duck
>>>>> Go, which has a TINY sliver of the search market)
>>>>>
>>>>
>>>> Compared to Google, *ALL* other search sites have "a tiny sliver of the
>>>> search market".  As I previously noted,
>>>> https://www.visualcapitalist.com/wp-content/uploads/2019/08/top-100-websites-ranking.html
>>>>  shows
>>>> that DuckDuckGo.com has had a 10-fold growth in the past 5 years, and gets
>>>> 30 MILLION HITS PER DAY.  While this is clearly nowhere near Google's
>>>> traffic stats, it's also clearly NOT trivial.
>>>>
>>>> But TiddlyWiki has no promotion mechanism. It's that initial "bump"
>>>>> that is the problem. People are turning away from TW
>>>>> before they know anything more because in their language the name says
>>>>> "Just a toy -- ok to ignore".
>>>>>
>>>>
>>>> Again, I think that you are vastly overstating the impact that a
>>>> product *name* has on decision-making.  Sure, some people will dismiss
>>>> TiddlyWiki "before they know anything more", but I 

Re: [tw5] Re: Consider renaming TiddlyWiki

2020-03-09 Thread Arlen Beiler
AtomicWiki
That's another idea. I think it captures the essence of TiddlyWiki.

Or the office suite :)
NoteWiki
SheetWiki
SlideWiki
TableWiki

More ideas
PageWiki

Coral Platform (the idea of living building blocks)




MinnoWiki seems to carry about as much appeal as TiddlyWiki (if you have no
negative connotation for the word "Tiddly"), I would think.

Arlen

On Mon, Mar 9, 2020 at 9:07 AM TiddlyTweeter 
wrote:

> My sense is that the real solution to TiddlyWiki gaining more traction in
>> the marketplace is about creating one or more compelling "killer apps" that
>> fill widely-perceived, but under-served demands for a particular set of
>> features rather than avoiding any general aversion to the underlying
>> TiddlyWiki name, and that changing the name will accomplish almost nothing
>> in this regard.
>
>
> Eric, am I allowed to agree with both you & Mark S. ? :-)
>
> The "killer apps" part of this I fully agree with. It simply makes sense
> to me to address niches with precise solutions, which is exactly what TW is
> spectacularly good at.
>
> And we may already have them but don't seem to have a way to advance them.
>
> So there is, maybe, a missing promo piece?
>
> Thoughts
> TT
>
> On Sunday, 8 March 2020 05:11:51 UTC+1, Eric Shulman wrote:
>>
>> On Saturday, March 7, 2020 at 5:05:36 PM UTC-8, Mark S. wrote:
>>>
>>> I think if we had stats, you'd find that basically there's about 350
>>> million people
>>>
>>
>> If we had stats... then we would have a number... but without stats,
>> saying "350 million" is just an imagined number.  This reminds of an old
>> saying: "86.3% of all statistics are made up on the spot" :)
>>
>>
>>> who will automatically discount a product that has a childish,
>>> non-serious, and embarrassing name like "Tiddly--anything".
>>>
>>
>> I think you are vastly overstating the "embarrassing" aspect.  I suspect
>> that is more of a personal response on your part, rather than some general
>> truth.  As I wrote previously:
>>
>> *REAL adults... evaluate the cost/benefit relationship to their
>> objectives, and adopt whatever tech makes sense to meet their goals.*
>>
>> Yes, there are PROMOTED products with childish names (e.g. Duck Duck Go,
>>> which has a TINY sliver of the search market)
>>>
>>
>> Compared to Google, *ALL* other search sites have "a tiny sliver of the
>> search market".  As I previously noted,
>> https://www.visualcapitalist.com/wp-content/uploads/2019/08/top-100-websites-ranking.html
>>  shows
>> that DuckDuckGo.com has had a 10-fold growth in the past 5 years, and gets
>> 30 MILLION HITS PER DAY.  While this is clearly nowhere near Google's
>> traffic stats, it's also clearly NOT trivial.
>>
>> But TiddlyWiki has no promotion mechanism. It's that initial "bump" that
>>> is the problem. People are turning away from TW
>>> before they know anything more because in their language the name says
>>> "Just a toy -- ok to ignore".
>>>
>>
>> Again, I think that you are vastly overstating the impact that a product
>> *name* has on decision-making.  Sure, some people will dismiss TiddlyWiki
>> "before they know anything more", but I believe that most people are not
>> quite that shallow, especially when they are looking for potential
>> solutions to their needs.
>>
>>
>>>  Yes, if there's an evangelizer in the room, they can get past that.
>>>
>>
>> This suggests that TiddlyWiki simply needs some more persuasive
>> "evangelizing"... and that doesn't necessarily mean someone "in the room".
>>
>> Consider a likely scenario:
>>
>> Someone is searching for "wiki" software.  They start by searching Google
>> for "wiki programs".  Among the top search results are several "wiki review
>> sites".  Being somewhat jaded by internet hype, they skip over the
>> "advertisement" links and the first few links, which appear to be minor
>> sites (www.clickonf5.org) or self-promoting (www.helpiewp.com, which
>> lists its own HelpieWiki first!).  The next Google search result is
>> https://en.wikipedia.org/wiki/List_of_wiki_software
>> ;
>> and Wikipedia is generally well-regarded as having reasonably objective and
>> useful information (except for certain controversial topics... of which
>> "wiki software" is NOT!)
>>
>> On that Wikipedia page, they find that TiddlyWiki is listed TWICE:
>>
>> First, under the "javascript-based" category, where it is described as
>>
>> *"...a HTML-JavaScript-based server-less wiki in which the entire
>>> site/wiki is contained in a single file"*
>>
>>
>> TiddlyWiki is also listed again, under the "personal wiki software"
>> category, where is it described as
>>
>> *"...a free, open-source personal use (single-machine) wiki based on
>>> HTML/JavaScript for any browser and OS. It supports customization and a
>>> wide range of addons."*
>>
>>
>> Thus, from this one lookup on Wikipedia, TiddlyWiki is already
>> "evangelized" as:
>> * server-less (ease of setup)
>> * single file 

Re: [tw5] Re: GitHub Security

2020-01-15 Thread Arlen Beiler
Guys, a public link is ALWAYS a public link. Never consider it protected in
any way if the link itself can get you all the way in without logging in at
all.

On Tue, Jan 14, 2020 at 14:41 Alfonso Arciniega  wrote:

> Re Dropbox, the easiest (for me at last) way is:
>
>
>1. Create a new account at DropPages: https://droppages.com/
>2. After signing in, create your site at:
>https://my.droppages.com/Account
>3. A folder will be created in your Dropbox account:
>https://www.dropbox.com/home/Apps/My.DropPages
>
>4. Inside this folder you will find a folder with the name of your
>site: [your_name_site].droppages.com]
>5. Again, inside you fill find three folders: Content, Public, and
>Templates. The starting site is a very, very basic landing website that you
>may ignore if all you want is a site for your TWs.
>6. Finally, put your TWs in the Public folder; and bookmark them as:
>https://[your_name_site].droppages.com/[my_TW.html]
>
>
> Your site and TWs remain private unless you give away the bookmarks.
> Updating your TWs are a easy as uploading them to the Public folder in your
> Dropbox. You may even want to create a separate email with a separate
> Dropbox account for this solely purpose.
>
> Note that DropPages will allow you to have up to two free sites: https://
> [your_name_site].droppages.com] with a total maximum of 50 MB.
>
> Alfonso
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/436b6551-5745-4fd0-8eee-fedc1e86405d%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSR8UKZ_SB5LW0VbM%2B843Sen4YwFNzsNSYZj7keiUCLsrQ%40mail.gmail.com.


Re: [tw5] Re: Please provide a working example of tiddlyserver settings.json with multiple directories and authentication?

2020-01-13 Thread Arlen Beiler
I'm sorry I'm not able to address this more thoroughly. I'm in the middle
of another project at the moment. I'm hoping to get back to TiddlyServer in
a few weeks.

One more thing, the options apply to all child folders as well. Also, the
same thing applies to groups, and a child group or folder will inherit the
parents properties unless it also has an options objects. In that case,
each property normally overrides the one above it, and inherits any not
specified.


On Mon, Jan 13, 2020, 23:14 Arlen Beiler  wrote:

> By $element: folder, I mean the literal string "folder".
>
> On Mon, Jan 13, 2020, 23:13 Arlen Beiler  wrote:
>
>> Instead of a folder string you use an object containing these properties
>>
>> $element: folder
>> key: optional custom alias (no slashes)
>> path: the folder string
>> $options: an array containing putsaver, backup, and auth options objects,
>> as desired.
>>
>> Now with that in mind, go to this section.
>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#auth-option,
>> which lists the properties for each of those options objects. Only the
>> $elements property is required, but the defaults are not specified, except
>> in the source code.
>>
>> I apologise for the confusion I created with that XML. I will remove it
>> and make that section clearer when I have time.
>>
>> On Mon, Jan 13, 2020, 19:38 Donald Coates  wrote:
>>
>>> Scott thank you so much taking the time to reply.  The thread is a
>>> little confusing since the first three posts are me talking to myself.  The
>>> second settings.json actually works.  The problem I was having in the
>>> beginning was I was accessing the server from localhost which is by default
>>> given all permissions so authorization didn't seem to be working.
>>>
>>> I have put the tiddlyserver on a vps and am running it in docker and
>>> authorization of both directories and tiddlywikis seems to be working
>>> fine.  My next step is to use nginx to handle https.  I can post what I
>>> have that works once I get everything working.
>>>
>>> One thing to note is in the authAccounts permissions section there is a
>>> hash for transfer: true that is not mentioned in the docs.  Also, I'm not
>>> sure but it may be required that a user group is defined.  It seems from
>>> the docs that the user group - which is defined as main user in my settings
>>> file and 'designgroup' in arlen's example file - is the key and the
>>> username:password,salt is the value.
>>>
>>> I'm not completely up on the lingo as you might be able to tell so I
>>> apologize if I'm using technical terms incorrectly
>>>
>>> .
>>>
>>> --
>>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/359fc795-e8ff-497c-b25e-63e423d0cce2%40googlegroups.com
>>> <https://groups.google.com/d/msgid/tiddlywiki/359fc795-e8ff-497c-b25e-63e423d0cce2%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQCk%3Do80x9vnKhYD%3DsL0%2Bvnz0GCO87XuXFn_2AYShXNYg%40mail.gmail.com.


Re: [tw5] Re: Please provide a working example of tiddlyserver settings.json with multiple directories and authentication?

2020-01-13 Thread Arlen Beiler
By $element: folder, I mean the literal string "folder".

On Mon, Jan 13, 2020, 23:13 Arlen Beiler  wrote:

> Instead of a folder string you use an object containing these properties
>
> $element: folder
> key: optional custom alias (no slashes)
> path: the folder string
> $options: an array containing putsaver, backup, and auth options objects,
> as desired.
>
> Now with that in mind, go to this section.
> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#auth-option,
> which lists the properties for each of those options objects. Only the
> $elements property is required, but the defaults are not specified, except
> in the source code.
>
> I apologise for the confusion I created with that XML. I will remove it
> and make that section clearer when I have time.
>
> On Mon, Jan 13, 2020, 19:38 Donald Coates  wrote:
>
>> Scott thank you so much taking the time to reply.  The thread is a little
>> confusing since the first three posts are me talking to myself.  The second
>> settings.json actually works.  The problem I was having in the beginning
>> was I was accessing the server from localhost which is by default given all
>> permissions so authorization didn't seem to be working.
>>
>> I have put the tiddlyserver on a vps and am running it in docker and
>> authorization of both directories and tiddlywikis seems to be working
>> fine.  My next step is to use nginx to handle https.  I can post what I
>> have that works once I get everything working.
>>
>> One thing to note is in the authAccounts permissions section there is a
>> hash for transfer: true that is not mentioned in the docs.  Also, I'm not
>> sure but it may be required that a user group is defined.  It seems from
>> the docs that the user group - which is defined as main user in my settings
>> file and 'designgroup' in arlen's example file - is the key and the
>> username:password,salt is the value.
>>
>> I'm not completely up on the lingo as you might be able to tell so I
>> apologize if I'm using technical terms incorrectly
>>
>> .
>>
>> --
>> 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 tiddlywiki+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/359fc795-e8ff-497c-b25e-63e423d0cce2%40googlegroups.com
>> <https://groups.google.com/d/msgid/tiddlywiki/359fc795-e8ff-497c-b25e-63e423d0cce2%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSR4Ok6HZMyNK%2Buf9XT6j1tZoRUqGfOEQLPg1tFynnK4xw%40mail.gmail.com.


Re: [tw5] Re: Please provide a working example of tiddlyserver settings.json with multiple directories and authentication?

2020-01-13 Thread Arlen Beiler
Instead of a folder string you use an object containing these properties

$element: folder
key: optional custom alias (no slashes)
path: the folder string
$options: an array containing putsaver, backup, and auth options objects,
as desired.

Now with that in mind, go to this section.
https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#auth-option,
which lists the properties for each of those options objects. Only the
$elements property is required, but the defaults are not specified, except
in the source code.

I apologise for the confusion I created with that XML. I will remove it and
make that section clearer when I have time.

On Mon, Jan 13, 2020, 19:38 Donald Coates  wrote:

> Scott thank you so much taking the time to reply.  The thread is a little
> confusing since the first three posts are me talking to myself.  The second
> settings.json actually works.  The problem I was having in the beginning
> was I was accessing the server from localhost which is by default given all
> permissions so authorization didn't seem to be working.
>
> I have put the tiddlyserver on a vps and am running it in docker and
> authorization of both directories and tiddlywikis seems to be working
> fine.  My next step is to use nginx to handle https.  I can post what I
> have that works once I get everything working.
>
> One thing to note is in the authAccounts permissions section there is a
> hash for transfer: true that is not mentioned in the docs.  Also, I'm not
> sure but it may be required that a user group is defined.  It seems from
> the docs that the user group - which is defined as main user in my settings
> file and 'designgroup' in arlen's example file - is the key and the
> username:password,salt is the value.
>
> I'm not completely up on the lingo as you might be able to tell so I
> apologize if I'm using technical terms incorrectly
>
> .
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/359fc795-e8ff-497c-b25e-63e423d0cce2%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdST6WJ30nt15Diq7r7bEVh48KyJvg%3DKRmG7gAULqYQN5ew%40mail.gmail.com.


Re: [tw5] Anyone good with bookmarklets? QUick config of tiddlywikis

2020-01-05 Thread Arlen Beiler
A link to a tiddler can be dragged into a different wiki, or dragged to the
bookmarks bar then dragged into another wiki for import. Also the best way
to load an external file would probably be to append a script tag with src
to the body. Haven’t tested it but it should work.

On Thu, Jan 2, 2020 at 08:57 TiddlyTweeter  wrote:

> TonyM
>
> Some comments.
>
> I have become very aware that you are keen on leverage of (a) browsers and
> (b) Windows to better support working with TW.
>
> These are things I am much in harmony with.
>
> I tried a few times to document some parts of this I know about. It is not
> as easy as it first looks to derive something that is comprehensible if you
> not been through it.
> Documentation is very time consuming & prone to error, so I tend to not
> publish it.
>
> The Bookmarklet by Jeremy is an elegant example of "just doing it" that is
> nicely contained.
>
> I continue to work on Polly, which is basically using shell functions to
> provide a management interface to save, backup, clone, fetch, launch, order
> etc wikis.
>
> BTW, Timimi (FF only) is interesting for single wiki in the way Bob is for
> file wike. It is quite easy in Timimi to launch scripts to do things.
> Closing the gap so you can do OS things via TW is real leverage
>
> New year thoughts.
> Best, 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/baaf8dae-f964-4a48-bfa3-869489a73250%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTaG%3DnyEnQ67eBKUG%2BeT99N%3DFBBahWOVYp3BuGZe5d%3DgQ%40mail.gmail.com.


Re: [tw5] Bob and TiddlyServer

2019-12-10 Thread Arlen Beiler
I’m not sure. Jed would probably know a lot better.

The main feature of TiddlyServer is organization. It lets you reference all
your various TiddlyWiki folders and universes across your drives and lets
you work with all of them from the browser without messing with different
ports and savers and all kinds of other hassles. It just works. The setup
is still rough but I’m working on improving that.

But other than adding a web socket layer, it tries to be completely
transparent, using existing TiddlyWiki technology under the hood. In fact,
most of the inspiration for it came from Jeremy because of the way he
designed the boot.js file and other server related components. The paradigm
he used is what made it possible. In a way, it felt like I built a section
of TiddlyWiki that had been planned for but never built. Maybe not, but
Jeremy definitely laid a solid foundation.

I tried to stay within the parameters of the TiddlyWiki core, and I am
confident that I succeeded. Other than adding a couple features to the
core, including the server post start hook and the boot completion
callback, I pretty much didn’t make any changes to TiddlyWiki, and I
definitely didn’t need to fork it.

A few features that are hopefully coming soon include a browser extension
which will be able to easily manage and setup the server (plus a few
bonuses like saving for file urls), and a plugin that automatically serves
the core from a CDN instead of your server to speed up page load
dramatically for online applications (it will include a fallback to
TiddlyServer in case the internet is offline, and downloads inside the wiki
should still be unaffected).

Bob has a lot more features than that, I believe, but I’ll let others
explain that part because I’m not familiar with it at the moment.

On Mon, Dec 9, 2019 at 14:45 Diego Mesa  wrote:

> Hello all,
>
> Its that time of the year again, where a *friend* of mine wants to know
> if the community could help clarify the differences between two major
> players: Bob and TiddlyServer, as well as Arlens newer creation/tests?
>
> Ill be sure to pass on your comments/observations to my friend!
>
> Best,
> Diego
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/7ac3f0a3-da45-4ba5-820f-f09cc3154d29%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTA2JjyMjihO4xSdXZE4GWJpQEqZNdG6mjfP-2Otpw74g%40mail.gmail.com.


Re: [tw5] Re: Inclusion of Whole MP3 Files

2019-12-09 Thread Arlen Beiler
There's something called canonical uri which lets you link external files
in a way that is similar to including it in the wiki, but I'm not sure
about the details. You should be able to find info on tiddlywiki.com.


On Thu, Dec 5, 2019 at 3:00 PM Qalisto  wrote:

> We thank Luis for this thorough explanation!
> ...
>
> On Wednesday, December 4, 2019 at 12:07:32 PM UTC, Luis Gonzalez wrote:
>>
>> I don't like to include big files inside the Tiddlywiki, so I create a
>> directory for all mp3 tracks. Then you have many ways of create the
>> tiddlers. I add an example.
>>
>> Unzip empty.zip and open empty.html:
>>
>>
>> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/1f656720-d0f0-43e8-b9f5-7f5b9fed864f%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSR1bC6C4sAO4bkk5O8OahRY%2BU7iLNSp_Yb50aT2aMXvbA%40mail.gmail.com.


Re: [tw5] Re: Best approach for multiple wikis

2019-12-09 Thread Arlen Beiler
sometimes browsers let you send script tags after the html tag is closed,
you could try inserting the directory entries in there. I use vscode, which
will give you intellisense help. I also recommend running npm install which
should give you the same npm dependancies as I use. Hopefully everything's
configured correctly. If it says it can't find a module, just let me know.

On Mon, Dec 9, 2019 at 8:08 AM Arlen Beiler  wrote:

> src/generateDirectoryListing.js
>
> On Sun, Dec 8, 2019 at 2:01 AM Mohammad 
> wrote:
>
>> Hi Arlen,
>>  Where is the landing page of TiddlyServer!
>> I gonna to give try if I can use TW for landing page!
>>
>> --Mohammad
>>
>> On Tuesday, December 3, 2019 at 11:30:43 PM UTC+3:30, Arlen Beiler wrote:
>>>
>>> Just thought I'd take a minute to chime in here. I made TiddlyServer to
>>> solve my own problem of Massive Multi-file Online wikis. It serves the
>>> folders you specify in a sort of tree allowing them to be grouped together
>>> and easily navigated with the built-in directory index (even the virtual
>>> directories or "groups"). When a data folder is accessed, TiddlyServer
>>> automatically fires up a node instance of the TiddlyWiki listen command and
>>> mounts it at that path, meaning it forwards all requests to the data folder
>>> Node server instance. This makes it work identical to the TiddlyWiki listen
>>> command for most normal uses of the listen command, except you can access
>>> multiple data folders on the same server. Single file wikis (TW 5.1.15 and
>>> newer) have a saver already built into them which TiddlyServer uses to save
>>> single file wikis. Single file wikis can be backed up automatically on
>>> every save, but data folders are on their own by design. I recommend
>>> using Git or Dropbox for that.
>>>
>>> There are a bunch of advanced options and even authentication, but the
>>> basics are enough for most people.
>>>
>>> It's pretty simple to use but I often notice people having trouble
>>> getting it installed, so I thought I'd throw in some install instructions I
>>> wrote some time ago.
>>>
>>> It's fine to just use master (well, aka v2.1 right now) right now:
>>> https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or
>>> Download" button then select your preferred download method. Cloning the
>>> repo is an easy way to get updates but downloading is fine too.
>>>
>>> Extract it to an empty folder so you don't risk merging with an existing
>>> folder. Once you extract it you can move it wherever you want it to be.
>>>
>>> https://nodejs.org/en/
>>>
>>> Go to NodeJS.org and download the LTS version of Node, which currently
>>> is 10.x, and install it on the computer you will be running TiddlyServer
>>> on. It's pretty straightforward, and the default options should work fine.
>>>
>>> You don't actually need to install the whole thing, you can also just
>>> download a zip file and extract node.exe into the TiddlyServer folder to
>>> make a portable install. Since you're working with IIS I'm sure you have
>>> enough computer experience know what I'm talking about, but if I'm not
>>> making myself clear, just install NodeJS like I described above.
>>>
>>> Now, here's the part that most people find tricky. Copy
>>> example-settings-quick.json and name it settings.json. That's the simplest
>>> setup. You can change the tree property to change what folders get served,
>>> but all html files and data folders inside it should just work out of the
>>> box.
>>>
>>> The entire documentation for the settings.json file is at
>>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and the
>>> tree property is the first item on the page. Here's a really simple example
>>> to get you started.
>>>
>>> "tree": {
>>> "myfolder": "../personal",
>>> "workstuff": "../work",
>>> "user": "~/Desktop/random",
>>> "projects_group": {
>>> "tiddlyserver": "~/Desktop/Github/TiddlyServer",
>>> "material-theme": "~/Dropbox/Material Theme"
>>> }
>>> }
>>>
>>>
>>> And that's all there is to it. Once you have your settings.json file
>>> setup, just run "node server.js" to start the server. TiddlyServer expects
>>> to find the settings.json file in 

Re: [tw5] Re: Best approach for multiple wikis

2019-12-09 Thread Arlen Beiler
src/generateDirectoryListing.js

On Sun, Dec 8, 2019 at 2:01 AM Mohammad  wrote:

> Hi Arlen,
>  Where is the landing page of TiddlyServer!
> I gonna to give try if I can use TW for landing page!
>
> --Mohammad
>
> On Tuesday, December 3, 2019 at 11:30:43 PM UTC+3:30, Arlen Beiler wrote:
>>
>> Just thought I'd take a minute to chime in here. I made TiddlyServer to
>> solve my own problem of Massive Multi-file Online wikis. It serves the
>> folders you specify in a sort of tree allowing them to be grouped together
>> and easily navigated with the built-in directory index (even the virtual
>> directories or "groups"). When a data folder is accessed, TiddlyServer
>> automatically fires up a node instance of the TiddlyWiki listen command and
>> mounts it at that path, meaning it forwards all requests to the data folder
>> Node server instance. This makes it work identical to the TiddlyWiki listen
>> command for most normal uses of the listen command, except you can access
>> multiple data folders on the same server. Single file wikis (TW 5.1.15 and
>> newer) have a saver already built into them which TiddlyServer uses to save
>> single file wikis. Single file wikis can be backed up automatically on
>> every save, but data folders are on their own by design. I recommend
>> using Git or Dropbox for that.
>>
>> There are a bunch of advanced options and even authentication, but the
>> basics are enough for most people.
>>
>> It's pretty simple to use but I often notice people having trouble
>> getting it installed, so I thought I'd throw in some install instructions I
>> wrote some time ago.
>>
>> It's fine to just use master (well, aka v2.1 right now) right now:
>> https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or
>> Download" button then select your preferred download method. Cloning the
>> repo is an easy way to get updates but downloading is fine too.
>>
>> Extract it to an empty folder so you don't risk merging with an existing
>> folder. Once you extract it you can move it wherever you want it to be.
>>
>> https://nodejs.org/en/
>>
>> Go to NodeJS.org and download the LTS version of Node, which currently is
>> 10.x, and install it on the computer you will be running TiddlyServer on.
>> It's pretty straightforward, and the default options should work fine.
>>
>> You don't actually need to install the whole thing, you can also just
>> download a zip file and extract node.exe into the TiddlyServer folder to
>> make a portable install. Since you're working with IIS I'm sure you have
>> enough computer experience know what I'm talking about, but if I'm not
>> making myself clear, just install NodeJS like I described above.
>>
>> Now, here's the part that most people find tricky. Copy
>> example-settings-quick.json and name it settings.json. That's the simplest
>> setup. You can change the tree property to change what folders get served,
>> but all html files and data folders inside it should just work out of the
>> box.
>>
>> The entire documentation for the settings.json file is at
>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html and the
>> tree property is the first item on the page. Here's a really simple example
>> to get you started.
>>
>> "tree": {
>> "myfolder": "../personal",
>> "workstuff": "../work",
>> "user": "~/Desktop/random",
>> "projects_group": {
>> "tiddlyserver": "~/Desktop/Github/TiddlyServer",
>> "material-theme": "~/Dropbox/Material Theme"
>> }
>> }
>>
>>
>> And that's all there is to it. Once you have your settings.json file
>> setup, just run "node server.js" to start the server. TiddlyServer expects
>> to find the settings.json file in the same directory (which is where I have
>> mine, which is why it's in .gitignore!).
>>
>> I made TiddlyServer simple because I want it to be simple for me to use
>> every day :)
>>
>> Hope that helps
>>
>> On Tue, Dec 3, 2019 at 9:02 AM Victor Dorneanu  wrote:
>>
>>> Hi TT,
>>>
>>> it's not really related to Github. I just use to store/backup my
>>> tiddlers. The backend storage is actually quite irrelevant. I just need
>>> some "best practices" / workflows that individuals have established over
>>> time in order to manage multiple wikis.
>>>
>>> Cheers,
>>> Victor
>>>
>>> On Tuesday, 

Re: [tw5] TiddlyWiki starting time is sooooo slow

2019-12-09 Thread Arlen Beiler
It is essentially a sandbox for each module. Disabling it is a little less
safe but not by much. The only way it matters is if a plugin or module
would modify a global like Promise or Buffer, but data folders and plugins
also have full file system access, which is much more powerful, so there's
actually not much that it can protect from. So for your application the
benefits definitely outweigh the risks.

I'm honestly not sure that this offers much additional security at all,
especially since the Node docs specifically say not to use it as a security
measure.

On Sun, Dec 8, 2019 at 3:52 PM Florian Cauvin 
wrote:

> Arlen,
> Yes, wow, this change made a *dramatic* improvement in TiddlyWiki startup
> time which was reduced from over a minute to about 3 seconds. Fantastic.
>
> So, can I keep TW running his way, is it somehow "less safe" or ...?
>
>
> On Saturday, December 7, 2019 at 8:31:11 PM UTC+2, Arlen Beiler wrote:
>>
>> Ok, here's the evalSandboxed code currently. Well, almost, there is one
>> change inside the function, but just ignore that.
>> /*
>> Run code in a sandbox with only the specified context variables in scope
>> */
>> $tw.utils.evalSandboxed = $tw.browser ? $tw.utils.evalGlobal : function(
>> code,context,filename) {
>> var sandbox = $tw.utils.extend(Object.create(null),context);
>> vm.runInNewContext(code,sandbox,$tw.utils.evalFilename(filename));
>> return sandbox.exports;
>> };
>>
>> In the first line, change *$tw.browser* to *true*, like this:
>>
>> /*
>> Run code in a sandbox with only the specified context variables in scope
>> */
>> $tw.utils.evalSandboxed = true ? $tw.utils.evalGlobal : function(code,
>> context,filename) {
>> var sandbox = $tw.utils.extend(Object.create(null),context);
>> vm.runInNewContext(code,sandbox,$tw.utils.evalFilename(filename));
>> return sandbox.exports;
>> };
>>
>> See if that improves anything.
>>
>> Arlen
>>
>> On Fri, Dec 6, 2019 at 10:28 AM Florian Cauvin 
>> wrote:
>>
>>> Thanks Arlen for the suggestions:
>>>
>>> The first is that evalSandboxed (in boot.js) runs every module in a new
>>>> context. If you change it to all of them using one separate context which
>>>> you create outside the function, it should speed things up some. This one
>>>> may vary between node versions, but it's worth a shot.
>>>>
>>>
>>> I located the file and function call you're refering to but I'm not
>>> familiar with Javascript, Node, or the internals of TiddlyWiki. Thus I
>>> don't feel confident trying to modify that code. Hopefully, a TiddlyWiki
>>> developer could look into this?
>>>
>>>
>>>> The second is loading the hundreds of tiddlers that make up the core.
>>>> There is a feature of the boot process that fixes this. Replace the
>>>> contents of the core folder with this file (assuming your using
>>>> Tiddlywiki5.1.21)
>>>> https://github.com/Arlen22/TiddlyWiki5-production/blob/master/5-1-21/core/plugin.info.
>>>> That way it's just loading one file and doing a simple JSON.parse.
>>>>
>>>
>>> Alright, I replaced all content of
>>> /usr/local/lib/node_modules/tiddlywiki/core with that file you linked
>>> to. It seems to have shaved a few seconds off the startup time which
>>> remained over 56 seconds, so while it seems to help a bit, there seems to
>>> be a larger issue.
>>>
>>> --
>>> 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 tiddl...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/b987363a-17f2--8bb9-d6aa43c7b841%40googlegroups.com
>>> <https://groups.google.com/d/msgid/tiddlywiki/b987363a-17f2--8bb9-d6aa43c7b841%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/2495b4d0-ff89-474e-8c67-ffae52549c9e%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/2495b4d0-ff89-474e-8c67-ffae52549c9e%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQUR1PjSFC25toy8%3DyWSz1598KPEOjf1%3DySnucQFJyrgw%40mail.gmail.com.


Re: [tw5] TiddlyWiki starting time is sooooo slow

2019-12-07 Thread Arlen Beiler
Ok, here's the evalSandboxed code currently. Well, almost, there is one
change inside the function, but just ignore that.
/*
Run code in a sandbox with only the specified context variables in scope
*/
$tw.utils.evalSandboxed = $tw.browser ? $tw.utils.evalGlobal : function(code
,context,filename) {
var sandbox = $tw.utils.extend(Object.create(null),context);
vm.runInNewContext(code,sandbox,$tw.utils.evalFilename(filename));
return sandbox.exports;
};

In the first line, change *$tw.browser* to *true*, like this:

/*
Run code in a sandbox with only the specified context variables in scope
*/
$tw.utils.evalSandboxed = true ? $tw.utils.evalGlobal : function(code,
context,filename) {
var sandbox = $tw.utils.extend(Object.create(null),context);
vm.runInNewContext(code,sandbox,$tw.utils.evalFilename(filename));
return sandbox.exports;
};

See if that improves anything.

Arlen

On Fri, Dec 6, 2019 at 10:28 AM Florian Cauvin 
wrote:

> Thanks Arlen for the suggestions:
>
> The first is that evalSandboxed (in boot.js) runs every module in a new
>> context. If you change it to all of them using one separate context which
>> you create outside the function, it should speed things up some. This one
>> may vary between node versions, but it's worth a shot.
>>
>
> I located the file and function call you're refering to but I'm not
> familiar with Javascript, Node, or the internals of TiddlyWiki. Thus I
> don't feel confident trying to modify that code. Hopefully, a TiddlyWiki
> developer could look into this?
>
>
>> The second is loading the hundreds of tiddlers that make up the core.
>> There is a feature of the boot process that fixes this. Replace the
>> contents of the core folder with this file (assuming your using
>> Tiddlywiki5.1.21)
>> https://github.com/Arlen22/TiddlyWiki5-production/blob/master/5-1-21/core/plugin.info.
>> That way it's just loading one file and doing a simple JSON.parse.
>>
>
> Alright, I replaced all content of
> /usr/local/lib/node_modules/tiddlywiki/core with that file you linked to.
> It seems to have shaved a few seconds off the startup time which remained
> over 56 seconds, so while it seems to help a bit, there seems to be a
> larger issue.
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/b987363a-17f2--8bb9-d6aa43c7b841%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTJBRR%2BqZv13Qopcksa6%2BCCBt6Jszdxwe%3DHKXD0kWLzTA%40mail.gmail.com.


Re: [tw5] TiddlyWiki starting time is sooooo slow

2019-12-07 Thread Arlen Beiler
You can google the specs for the raspberry pi 3, but it’s about what you
described. And yes, it’s either a USB or MicroSD that it’s reading from,
but that problem was already eliminated by the core plugin file fix above
and it still takes 56 seconds for TiddlyWiki Node to load the core and run
the version command, so there’s more to be investigated. It could still be
paging to disk, as you mentioned, but the TiddlyWiki boot sequence will
only read about 7 files in this case.

On Sat, Dec 7, 2019 at 10:54 Chuck R.  wrote:

>
>
> On Saturday, December 7, 2019 at 12:18:16 AM UTC-5, TonyM wrote:
>>
>> that would mean something is broken then?
>>
>>
> Not necessarily broken with TW. The Rpi 3 is limited to 1-2GB of RAM AFAIK
> and we don't know how much RAM the OP has. One question I have is, if the
> TW file is a zip file (my assumption), then on average, all the compression
> of the text (which includes user-entered content and source code) is about
> 70%. So a 1GB compressed file compressed at 70% (or is 30% of the original
> size) has an uncompressed size of 1GB/0.30 or 3.3GB, beyond the RAM
> capacity of the RPI3. So when the Raspbian OS runs out of RAM, it starts
> paging RAM to a file (possibly on a micro SD card) frantically, and that's
> why it takes so long.
>
> Also, how big is each tiddler and how many images are in the TW file, and
> how big are the image files? Those are all variables I'd like to know
> about.
>
> Also the Rpi 3 is a low end CPU and it's not that fast.
>
> So I'd like to know:
>
>1. How much RAM does the RPi3 have?
>2. Is the OS on a micro SD card, USB hard drive, or something else?
>3. How big is the TW html file (which is the compressed size)?
>
>
> Another question is, when TW is opened (and it sounds like the OP is using
> the node.js version of TW), how often is the disk accessed? Since Rpi could
> be running off a micro-sd card, or USB hard drive. Throughput of USB is not
> that great and has never, IME, reached theoretical speeds. USB throughput
> IME has only reached 10% of theoretical speeds on average, and not much
> more than that.
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/f7b1fc7c-68bf-4db5-8cfb-5de854b3e78d%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQkmadMQ%3D8%3DNAaD3S2T82L1A2D%3Dhi8rf2jO_6Y8AOYQwA%40mail.gmail.com.


Re: [tw5] TiddlyWiki starting time is sooooo slow

2019-12-07 Thread Arlen Beiler
No. It’s a problem I’ve run into before. Slow processor speed is the main
culprit I think. What version of node are you using?

On Sat, Dec 7, 2019 at 00:18 TonyM  wrote:

> that would mean something is broken then?
>
> On Saturday, December 7, 2019 at 2:48:57 PM UTC+11, Arlen Beiler wrote:
>>
>> I just realized he was timing the runtime of the --version flag, which
>> would literally load only the core plugin and nothing else. So that's
>> almost 90 seconds to just load the core.
>>
>>>
>>> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/629be1bd-3763-419a-a5a7-dd94d3679b1f%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/629be1bd-3763-419a-a5a7-dd94d3679b1f%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTQ3ymxrbHeXwgv0Tb_B5Mjki3o%3Dtq0rqfWF8Om8EaiAg%40mail.gmail.com.


Re: [tw5] TiddlyWiki starting time is sooooo slow

2019-12-06 Thread Arlen Beiler
I just realized he was timing the runtime of the --version flag, which
would literally load only the core plugin and nothing else. So that's
almost 90 seconds to just load the core.

On Fri, Dec 6, 2019 at 9:29 PM TonyM  wrote:

> Florian,
>
> Add a Splash screen to startup if not already and consider the larger part
> of the load time could be the final render, depending on what is visible at
> startup. Minimise the tiddlers opened, hide the sidebar and more. Test a
> load with minimal opening and no features and unusual plugins active to see
> if this render time is a contributor.
>
> There are also performance indicators that can be activated to investigate
> this (Which I have not yet used.)
>
> Regards
> Tony
>
> On Saturday, December 7, 2019 at 2:28:24 AM UTC+11, Florian Cauvin wrote:
>>
>> Thanks Arlen for the suggestions:
>>
>> The first is that evalSandboxed (in boot.js) runs every module in a new
>>> context. If you change it to all of them using one separate context which
>>> you create outside the function, it should speed things up some. This one
>>> may vary between node versions, but it's worth a shot.
>>>
>>
>> I located the file and function call you're refering to but I'm not
>> familiar with Javascript, Node, or the internals of TiddlyWiki. Thus I
>> don't feel confident trying to modify that code. Hopefully, a TiddlyWiki
>> developer could look into this?
>>
>>
>>> The second is loading the hundreds of tiddlers that make up the core.
>>> There is a feature of the boot process that fixes this. Replace the
>>> contents of the core folder with this file (assuming your using
>>> Tiddlywiki5.1.21)
>>> https://github.com/Arlen22/TiddlyWiki5-production/blob/master/5-1-21/core/plugin.info.
>>> That way it's just loading one file and doing a simple JSON.parse.
>>>
>>
>> Alright, I replaced all content of
>> /usr/local/lib/node_modules/tiddlywiki/core with that file you linked
>> to. It seems to have shaved a few seconds off the startup time which
>> remained over 56 seconds, so while it seems to help a bit, there seems to
>> be a larger issue.
>>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/654d317b-af72-4e89-aa71-2ceabb26c17a%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQ4q6c-arvSxmJV7DJ%3DvFhatnUOQsFrNokPmoV0g5%2BUcQ%40mail.gmail.com.


Re: [tw5] Taking Node Server to the next level

2019-12-06 Thread Arlen Beiler
All three of those sites have an OAuth flow setup for that. Basically you
get redirected to the login page and then the login page returns a code
back to the client page. Wordpress might just involve using the browser
session, though, I’m not sure.

On Fri, Dec 6, 2019 at 07:58 bimlas  wrote:

> Arlen,
>
> WordPress (that's an interesting but very feasible suggestion), Google,
>> and Github all support multi-user editing natively, so each user would have
>> their own login credentials.
>>
>
> True, but we want to access the API with the saver, so we need a Personal
> Access Token. Or is it possible to use the API with native user
> credentials?
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/9d41a1f9-5d7f-4384-8385-2689c29d0cfc%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTCVr4be4e8rgegpuZFKbDg5T5YStx0QFEsObNQjhWvAw%40mail.gmail.com.


Re: [tw5] TiddlyWiki starting time is sooooo slow

2019-12-06 Thread Arlen Beiler
In my experience, there are two things which are the main startup
bottlenecks.

The first is that evalSandboxed (in boot.js) runs every module in a new
context. If you change it to all of them using one separate context which
you create outside the function, it should speed things up some. This one
may vary between node versions, but it's worth a shot.

The second is loading the hundreds of tiddlers that make up the core. There
is a feature of the boot process that fixes this. Replace the contents of
the core folder with this file (assuming your using Tiddlywiki5.1.21)
https://github.com/Arlen22/TiddlyWiki5-production/blob/master/5-1-21/core/plugin.info.
That way it's just loading one file and doing a simple JSON.parse.

That's the main ones I've found.

Arlen

On Fri, Dec 6, 2019 at 8:32 AM Florian Cauvin 
wrote:

> Hi Jeremy,
> I have a few hundreds tiddlers, but I don't think that's a huge amount of
> content.
>
> Starting time is not a show stopper (as once it's up and running,
> TiddlyWiki server performs very well), but it is definitely an annoyance
> which introduce friction in my workflow because I maintain many personal
> wikis and serve one wiki at a time (when I want to browse or edit it). Thus
> I often stop and then start Node.js to switch the current wiki I'm working
> with. In this case, it'd be very useful if it would load fast (which I
> guess should be possible as TW shouldn't need to deeply process all
> tiddlers' content just to start up).
>
> Cheers!
>
> On Friday, December 6, 2019 at 1:50:54 PM UTC+2, Jeremy Ruston wrote:
>>
>> Hi Florian
>>
>> Do you have a large number of tiddlers in your wiki?
>>
>> The startup time under Node.js hasn’t had much optimisation attention,
>> and I think there’s quite a lot of scope to improve things.
>>
>> Best wishes
>>
>> Jeremy.
>>
>> On 6 Dec 2019, at 11:33, Florian Cauvin  wrote:
>>
>> On my RaspberryPi 3 with Raspian and NodeJs:
>>
>> $ time tiddlywiki --version
>> 5.1.21
>>
>> real 1m2,309s
>> user 1m2,727s
>> sys 0m0,511s
>>
>>
>> Once TiddlyWiki is "loaded" it works well and is responsive but >1
>> minute to start up? Is that normal???
>>
>> --
>> 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 tiddl...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/34128edc-f5b0-4154-9077-2d38e79d1eee%40googlegroups.com
>> 
>> .
>>
>>
>> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/6513caf7-b1a4-4290-8abb-4718c3c9e292%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSeYHuJaKneM4Z569Xeod82M%3D_6EEF%3D0w5LK1PBF6OoKA%40mail.gmail.com.


Re: [tw5] Re: A client-side datafolder - Working Prototype

2019-12-06 Thread Arlen Beiler
A bag is a group of tiddlers. Currently each TiddlyWiki5 is one bag, for
example. A recipe loads a list of bags in order with higher priority
overriding lower priority. Saving works in a similar fashion. It's
something from the TiddlyWiki classic days that newer users are probably
not familiar with but long-time users have mentioned it to me quite a few
times.

The advantages of this format are numerous, but the primary reason for this
is that we don't need to load a TiddlyWIki instance on the server. So
instead of having a big tiddler store in memory on the server (times x
number of wikis when using TiddlyServer), we can keep that all on disk,
which saves a lot of memory for large wikis. There are a couple problems I
need to check yet related to saving and loading individual tiddlers, but
I'm quite excited about the state of things so far.

The problem this is trying to solve is that we can never assume that a data
folder supports loading disk tiddlers directly into the browser. The
TiddlyWiki server has configuration options that let it act more like a CMS
than a data folder. In other words, the tiddlers could be changed majorly
between the client and the disk, or the data folder could contain
configuration tiddlers that are only meant for the server and are excluded
from the client. Server startup modules could change anything and
everything about the way tiddlers are stored on disk, and so on. So we
needed to come up with a new format that bypasses that and guarantees that
we are looking at a client-side representation of the tiddler without
loading the datafolder environment.

What this then allows us to do is generate an HTML index file which is the
TiddlyWiki generated by the server as the page itself, then use whatever
mechanism we want to use to lazy-load the rest of the tiddlers into the
browser.

   - For TW Cloud, this means we can download a zip of the tiddlyweb folder
   and load it into the browser directly, then save changes back to Dropbox.
   You get all the benefits of data folders, without having to load a second
   "server" instance into the browser to run along side the "client" and
   translate the tiddlers between the two. That's what I would have had to do
   to support data folders on TW Cloud.
   - Noteself already uses client-side tiddler storage. Hopefully this
   concept can be expanded on for multi-user scenarios and the like.
   - If it works with TW cloud, it can easily work with most other cloud
   connector out there, including GitHub.
   - The concept of recipes will make it a lot easier to setup multi-user
   wikis with shared spaces and user spaces.
   - And the most important of them all: *TiddlyWiki client-side data
   folder handling can be translated into PHP*. So we can run this on any
   shared hosting, and seemlessly transfer it between the PHP and NodeJS
   realm, because it will be the same data folder. We will still need to
   generate the initial page using NodeJS, but that's pretty much expected
   anyway, I think.

Sorry, I know it's a lot. I hope it's all clear. I'm pretty excited about
the possibilities.

Arlen

On Thu, Dec 5, 2019 at 11:44 PM TonyM  wrote:

> Arlen
>
> Thanks for experimenting and innovating. Unfortunatly you have used some
> terminology that was common in the past such as bags and recipes.
>
> A short dummies guide in plain English would help us dummies understand
> more without having to go looking for definitions. Or perhaps you can
> reference some doco on these.
>
> If armed I can contribute more.
>
> Thanks
> Tony
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/63076535-69c9-45c0-98c5-0d628ddfc2d5%40googlegroups.com
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSCwbJSeBNL63oQRzStge43ZETcnv46omWAkhYPsXKOpg%40mail.gmail.com.


Re: [tw5] Taking Node Server to the next level

2019-12-06 Thread Arlen Beiler
WordPress (that's an interesting but very feasible suggestion), Google, and
Github all support multi-user editing natively, so each user would have
their own login credentials.

On Fri, Dec 6, 2019 at 6:54 AM bimlas  wrote:

> Jeremy, TonyM,
>
> Another interesting sync adaptor would be one that *retrieved *and stored
>> tiddlers via the Wordpress API.
>
>
> I think the main problem with "database backends" (Google Sheets,
> Wordpress, PouchDB) is that by default they are not accessible as a web
> page, but everyone has to set up credentials to read and edit the wiki.
> Sorry if I misunderstood it but haven't used Tiddly in this way. If I
> understand it, something like a database backend would look like this:
>
> * You open an empty Tiddly
> * Configure credentials for the saver
> * Saver synchronizes (downloads) tiddlers
> * When you make changes, the changes are saved to the database
>
> If it doesn't work that way, I apologize and please someone write down the
> workflow.
>
> The problem is you don't always want to give credentials - for example,
> you want to make tw.com visible without logging in. The easiest way to
> make your wiki public is to recreate the HTML (which anyone can read) after
> each change, and if you have credentials, you can also edit the tiddlers
> via this generated HTML. I find GitHub / GitLab best suited for this
> workflow, thanks to continous deployment.
>
> I would love to enable contributions to tiddler content via got hub a bit
>> like when you edit tiddlywiki.com but have the changes appear online.
>
>
> A workaround is to add new Personal Access Tokens to the repository, one
> for each user, so they will have their own "TiddlyWiki password".
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/3f3dd877-878f-4ad3-9c4c-4b8bc752567c%40googlegroups.com
> 
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQgknNyMWWvxZ-y1r51jhfRwvZtpw_4kQSA3PBuoU21aQ%40mail.gmail.com.


Re: [tw5] Re: Best approach for multiple wikis

2019-12-05 Thread Arlen Beiler
In this case the etag, while basically the same idea, is handled by the
browser-side TiddlyWiki and is stored in the pages JavaScript, so it isn't
affected by the cache. This problem is usually server-side or disk-side --
its rarely related to the browser.

On Thu, Dec 5, 2019 at 4:25 PM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> After speed-reading wikipedia, it seems to me that if the browser's cache
> doesn't update correctly, it might hang on to a 6 hour old etag value. I've
> noticed firefox doing this in other capacities. For instance, after
> reloading a list of my current reading, items that were previously
> unchecked will still show. I will have to load the page a second time in
> order to display the correct values.
>
> On Thursday, December 5, 2019 at 1:11:21 PM UTC-8, Mark S. wrote:
>>
>> I think I need an explainer about what an "etag" is. There are etags in
>> the vim editor, but I don't think you mean the same thing.
>>
>> Just to repeat. Between one save and a second attempted save was more
>> like 6 minutes, not 6 hours. But I don't understand what the etag is and
>> how it gets set.
>>
>> Thanks!
>>
>> On Thursday, December 5, 2019 at 12:55:52 PM UTC-8, Arlen Beiler wrote:
>>>
>>> You can disable etag checking completely if you want. If you can include
>>> some more examples from the log file that would be great as well.
>>>
>>> The relevant log file info here shows the two values, ifmatch being the
>>> browser copy. The last number is the modified timestamp in milliseconds,
>>> which as you can see in this case are 6 hours apart. If you google
>>> "epoch converter" you can paste that into "1970 Epoch in Milliseconds"
>>> converter to get the date. The third line (and similar lines in more
>>> serious scenarios) are debug lines where TiddlyServer points out which
>>> parts are different and caused the etag to fail.
>>>
>>> 412 ifmatch "0-5124547-*1575414313000*"
>>> 412 etag "0-5124547-*1575434388000*"
>>> *412 caused by difference in modified*
>>> [2019-12-03T20:46:07.125-0800] PUT 127.0.0.1   412 127.0.0.1
>>> /TW2014/T
>>> o.html   42.922 ms - -
>>>
>>> The docs for the putsaver.etag setting is here:
>>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#etag-string
>>> <https://www.google.com/url?q=https%3A%2F%2Farlen22.github.io%2Ftiddlyserver%2Fdocs%2Fserverconfig.html%23etag-string=D=1=AFQjCNFwKrGHpGLE1r68GWgYnUkoFBkqmA>
>>>
>>> The section docs
>>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#section-putsaver
>>>  has
>>> an example snippet.
>>>
>>> Alternatively, you can set etagAge (which is seconds, default of 3) to a
>>> ridiculously high number (like 2 hours) so it only checks the size and not
>>> the timestamp. But remember that the etag is gotten when the file is
>>> loaded, so even if it sits in your browser for six hours, it will still be
>>> the same if the file has not been modified on disk since then. There are
>>> various reasons why this could happen, which is why I added the etagAge
>>> setting. Another user had the same problem and we thought it seemed like
>>> the antivirus was changing the modified timestamp on certain drives for
>>> some reason.
>>>
>>> Hope that helps.
>>> Arlen
>>>
>>> On Wed, Dec 4, 2019 at 11:07 AM 'Mark S.' via TiddlyWiki <
>>> tiddl...@googlegroups.com> wrote:
>>>
>>>> Unless my computer has discovered time travel, there is no way the file
>>>> on disk is 6 hours newer.
>>>>
>>>> I load.
>>>> I save once.
>>>> I do things in the TW
>>>> I save again ... and get the error.
>>>>
>>>> So unless the file was saved with a timestamp 6 hours in the future, it
>>>> should be several minutes *older* than the browser version at the time of
>>>> the save.
>>>>
>>>> I'm using 5.1.21
>>>>
>>>> I'm wondering why it checks the time at all. Unless I do something
>>>> crazy like manually copy a different version to the directory, the browser
>>>> version should be "king".
>>>>
>>>> Perhaps checking the date slows things down. It's noticeably slower
>>>> saving a single-file wiki with TS than with BobSaver or file-backups.
>>>>
>>>> Tha

Re: [tw5] Re: Best approach for multiple wikis

2019-12-05 Thread Arlen Beiler
Yes, user-relative paths use the NodeJS os module to get the user's home
directory. All other paths use NodeJS path.resolve, with the absolute path
to the settings.json file as the first argument, which means that if NodeJS
path module thinks a path is not absolute, it will use settings.json as the
source for the relative path.

On Thu, Dec 5, 2019 at 4:23 PM Mohammad  wrote:

> Hi Arlen,
>
> More feedback
>
> I understood that we can keep TiddlyServer2.1 in separate folder from
> setting.json. So I think the below description may be helpful for new users
>
> --On Windows 10
>
>
>- After testing TiddlyServer one can have a setting directory to keep
>*setting.json*
>- The setting folder (directory) can be placed any where like
>"C:\Users\Mohammad\Documents" (Mohammad can be another name for other user)
>- In the setting directory one can have a batch file to start the
>server like *startServer.cmd* as below
>
> REM TiddlyServer 2.1
>
> node D:\TiddlyServer-2.1\server.js settings.json
>
>
>- Other folder can be in the parent folder of setting directory
>
> Example:
>  If the setting.json is locted under C:\TW\TiddlyServer2.1 then
>
> -- C:
>  TW
> -- TiddlyServer
> -- *setting.js*
> ---*startServer.cmd*
> -- Personal
> ---Working
> ---Sandbox
> ---backups
>
> This is while TiddlerServer itself is located in C:\Program
> Files\TiddlyServer2.1
> Dont forget backups which is used to backup single file wikis
>
> One question:
>
> I see Tiddlyserver knows path like ~\Desktop? Does it also recognize
> absolute path?
>
>
> --Mohammad
>
>
>
> On Tuesday, December 3, 2019 at 11:30:43 PM UTC+3:30, Arlen Beiler wrote:
>>
>> Just thought I'd take a minute to chime in here. I made TiddlyServer to
>> solve my own problem of Massive Multi-file Online wikis. It serves the
>> folders you specify in a sort of tree allowing them to be grouped together
>> and easily navigated with the built-in directory index (even the virtual
>> directories or "groups"). When a data folder is accessed, TiddlyServer
>> automatically fires up a node instance of the TiddlyWiki listen command and
>> mounts it at that path, meaning it forwards all requests to the data folder
>> Node server instance. This makes it work identical to the TiddlyWiki listen
>> command for most normal uses of the listen command, except you can access
>> multiple data folders on the same server. Single file wikis (TW 5.1.15 and
>> newer) have a saver already built into them which TiddlyServer uses to save
>> single file wikis. Single file wikis can be backed up automatically on
>> every save, but data folders are on their own by design. I recommend
>> using Git or Dropbox for that.
>>
>> There are a bunch of advanced options and even authentication, but the
>> basics are enough for most people.
>>
>> It's pretty simple to use but I often notice people having trouble
>> getting it installed, so I thought I'd throw in some install instructions I
>> wrote some time ago.
>>
>> It's fine to just use master (well, aka v2.1 right now) right now:
>> https://github.com/Arlen22/TiddlyServer -- Click the green "Clone or
>> Download" button then select your preferred download method. Cloning the
>> repo is an easy way to get updates but downloading is fine too.
>>
>> Extract it to an empty folder so you don't risk merging with an existing
>> folder. Once you extract it you can move it wherever you want it to be.
>>
>> https://nodejs.org/en/
>>
>> Go to NodeJS.org and download the LTS version of Node, which currently is
>> 10.x, and install it on the computer you will be running TiddlyServer on.
>> It's pretty straightforward, and the default options should work fine.
>>
>> You don't actually need to install the whole thing, you can also just
>> download a zip file and extract node.exe into the TiddlyServer folder to
>> make a portable install. Since you're working with IIS I'm sure you have
>> enough computer experience know what I'm talking about, but if I'm not
>> making myself clear, just install NodeJS like I described above.
>>
>> Now, here's the part that most people find tricky. Copy
>> example-settings-quick.json and name it settings.json. That's the simplest
>> setup. You can change the tree property to change what folders get served,
>> but all html files and data folders inside it should just work out of the
>> box.
>>
>> The entire documentation for the settings.json file is at
>> https://arlen22.github.io/tiddlyserver/

Re: [tw5] Re: Best approach for multiple wikis

2019-12-05 Thread Arlen Beiler
You can disable etag checking completely if you want. If you can include
some more examples from the log file that would be great as well.

The relevant log file info here shows the two values, ifmatch being the
browser copy. The last number is the modified timestamp in milliseconds,
which as you can see in this case are 6 hours apart. If you google
"epoch converter" you can paste that into "1970 Epoch in Milliseconds"
converter to get the date. The third line (and similar lines in more
serious scenarios) are debug lines where TiddlyServer points out which
parts are different and caused the etag to fail.

412 ifmatch "0-5124547-*1575414313000*"
412 etag "0-5124547-*1575434388000*"
*412 caused by difference in modified*
[2019-12-03T20:46:07.125-0800] PUT 127.0.0.1   412 127.0.0.1
/TW2014/T
o.html   42.922 ms - -

The docs for the putsaver.etag setting is here:
https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#etag-string

The section docs
https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#section-putsaver
has
an example snippet.

Alternatively, you can set etagAge (which is seconds, default of 3) to a
ridiculously high number (like 2 hours) so it only checks the size and not
the timestamp. But remember that the etag is gotten when the file is
loaded, so even if it sits in your browser for six hours, it will still be
the same if the file has not been modified on disk since then. There are
various reasons why this could happen, which is why I added the etagAge
setting. Another user had the same problem and we thought it seemed like
the antivirus was changing the modified timestamp on certain drives for
some reason.

Hope that helps.
Arlen

On Wed, Dec 4, 2019 at 11:07 AM 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> Unless my computer has discovered time travel, there is no way the file on
> disk is 6 hours newer.
>
> I load.
> I save once.
> I do things in the TW
> I save again ... and get the error.
>
> So unless the file was saved with a timestamp 6 hours in the future, it
> should be several minutes *older* than the browser version at the time of
> the save.
>
> I'm using 5.1.21
>
> I'm wondering why it checks the time at all. Unless I do something crazy
> like manually copy a different version to the directory, the browser
> version should be "king".
>
> Perhaps checking the date slows things down. It's noticeably slower saving
> a single-file wiki with TS than with BobSaver or file-backups.
>
> Thanks!
>
> On Wednesday, December 4, 2019 at 7:19:38 AM UTC-8, Arlen Beiler wrote:
>>
>> In this particular case, the file on disk is 6 hours newer than the copy
>> the browser downloaded. I have not used this feature of TiddlyServer much
>> so perhaps I should take a look at it again, but nothing changed since I
>> made it that I know of. I did run into a scenario where the etag was
>> changing by a second or two, so I added the putsaver.etagAge option to set
>> the window within which to ignore it. I will check the code to make sure
>> everything looks good on my end. What version of TiddlyWiki is the file?
>>
>> On Tue, Dec 3, 2019 at 11:53 PM 'Mark S.' via TiddlyWiki <
>> tiddl...@googlegroups.com> wrote:
>>
>>> I get "changed on server" messages regularly.  Often on the second time
>>> I attempt to save. Talking single files.
>>> This didn't happen with the old (1.??) version. It's made it pretty hard
>>> to use, since every time it happens I
>>> have to do a "rescue" of the changed tiddlers. If it just ignored the
>>> non-existent changes on disk and saved
>>> it would be fine. Output below.
>>>
>>> 412 ifmatch "0-5124547-1575414313000"
>>> 412 etag "0-5124547-1575434388000"
>>> 412 caused by difference in modified
>>> [2019-12-03T20:46:07.125-0800] PUT 127.0.0.1   412 127.0.0.1
>>> /TW2014/T
>>> o.html   42.922 ms - -
>>>
>>> Thanks!
>>>
>>> Just thought I'd take a minute to chime in here. I made TiddlyServer to
>>>> solve my own problem of Massive Multi-file Online wikis. It serves the
>>>> folders you specify in a sort of tree allowing them to be grouped together
>>>> and easily navigated with the built-in directory index (even the virtual
>>>> directories or "groups"). When a data folder is accessed, TiddlyServer
>>>> automatically fires up a node instance of the TiddlyWiki
>>>>
>>> --
>>> You received this message because you are subscribed to the Google

[tw5] A client-side datafolder - Working Prototype

2019-12-05 Thread Arlen Beiler
I have a working prototype for the client-side data folders. The reason I
call them client-side is because they are stored on disk exactly as they
appear on the client, and are deserialized directly from disk when
requested.

The client tiddlers are lazy loaded, which TiddlyWiki has supported for
several years. The browser side of things literally worked "out of the
box", but the server-side took quite a bit of thought and structure to work
out the details.

I've also decided to bring back more of the TiddlyWeb protocol, although I
don't know how far I will go with it yet. So the server side supports
multiple bags and recipes but the details are not finalized yet.

It's really simple to test and it should just work. Just download the repo
at
https://github.com/Arlen22/TW5-storage-plugin/tree/7ef9625eb796e115282b15180262f6a2c6d9cc19
and
follow the instructions in the readme.

I expect to add more features later once I hear from you all what your
thoughts are.

Arlen

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSR7MVNFiMT-MZK-KD6Q0%2BNFNPoknkm3BQQrn%3DGirPuoBg%40mail.gmail.com.


  1   2   3   4   5   6   7   >