Thanks for sharing this monitoring tool!
On Monday, April 20, 2020 at 11:53:27 PM UTC+4:30, Arlen Beiler wrote: > > 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 < > [email protected] <javascript:>> 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 < >>> [email protected] <javascript:>> 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 < >>>>> [email protected] <javascript:>> 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 [email protected] <javascript:>. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/tiddlywiki/9bc1ec76-a308-472c-b99c-f66e5dd31519%40googlegroups.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/tiddlywiki/9bc1ec76-a308-472c-b99c-f66e5dd31519%40googlegroups.com?utm_medium=email&utm_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 [email protected] <javascript:>. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/tiddlywiki/a43e8862-e062-44a4-8618-e5c3a6020cc7%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/tiddlywiki/a43e8862-e062-44a4-8618-e5c3a6020cc7%40googlegroups.com?utm_medium=email&utm_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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywiki/ace3fe81-0b6c-49bc-b9dd-2ac3e25ad712%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tiddlywiki/ace3fe81-0b6c-49bc-b9dd-2ac3e25ad712%40googlegroups.com?utm_medium=email&utm_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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1a5df424-48ae-4f6d-b95d-155f83b978c4%40googlegroups.com.
