Folks, Just a Quick word on saving and changes within your browser. Even without the local storage plugin active your changes often remain in the browser tabs memory until you close the tab or browser. If in doubt use an emergency saver and you can import the tiddlers back in later. However some tiddlers that change should not be re-imported as they are created by server processes not you, the interactive user. If I know I only edited a few tiddlers I sometimes just drag and drop them on a separate "scratch wiki", a copy of empty.html the I can reload the tab/browser. One approach is to set the usernames and export only tiddlers that were modified by your user name.
One area that is a little less intuitive for people is the space and memory requirements. This has a remedy if you are a big tiddlywiki user as "90% of the Day 90% of my work" is done in various tiddlywikis, many in chrome and Firefox. This means my key applications are browsers, rather than native apps. Browsers are often designed to be the browser on your device, and they limit their total memory consumption so as to not overwhelm memory and slow you local apps. From memory Chrome and FireFox manage their RAM within 2GB limits by default. On my 16GB desktop I would thus be using two browsers and only 4GB of my available ram all day. With almost 12Gb unused. They were hard to find, and I have lost them since but you can increase the browsers RAM usage limit for performance gains if you are a big browser user, which you are if you are a big tiddlywiki user. Both my browsers use 4GB + now and performance is great. Also maintaining your local drive to have adequate space remaining, 20%+ is wise so the browser or operating system does not try and recover space by clearing caches etc... A Lot of people work to actively reduce the RAM and disk their browser uses and the browsers are designed to do this them-self, but big browser users should consider taking the opposite approach and give there browsers a lot of headroom. Regards Tony On Sunday, June 28, 2020 at 10:47:44 PM UTC+10, Enrico wrote: > > Hi, > I am writing to figure out whether I could have done something to prevent > this pretty bad data loss into which I incurred yesterday, so it does not > happen again. > > *My tiddlywiki setup* > I run the node.js tiddlywiki5 as a systemd service on a virtual private > server. > It's served from a public IP address (protected by username/password > login). > Apache webserver acts as a proxy between the outside world and the > `tiddlywiki --serve` process. > `tiddlywiki -version` prints "5.1.22". > > > *What happened* > Some days ago I copied over some tiddlers from another tiddlywiki, > restarted the tiddlywiki service, checked that I could access old as well > as new tiddlers, and happily went along with my life. > At some point, the server process started printing errors that I > absolutely did not notice (100% my fault for not checking my server logs > for a few days). > Here's the error message that was printed in a loop, always about the "Eye > Divers" tiddler: > > vultr.guest tiddlywiki[22081]: syncer-server-filesystem: Dispatching > 'save' task: Eye Divers > vultr.guest tiddlywiki[22081]: Sync error while processing save of 'Eye > Divers': Error: EACCES: permission denied, open > '/home/tiddlywikirunner/tiddlyme/tiddlers/Eye > Divers.tid' > > When I finally noticed these errors, yesterday, I copied the content of > the "Eye Divers" tiddler to my clipboard and restarted the tiddlywiki > service. > Result: *all tiddlers that I have created in the past few days have been > lost*. It turns out that the problem with the "Eye Divers" tiddler > prevented the tiddlywiki process from saving any new tiddler to disk. > > *The problem* > The main problem is that I had no way to know that all those tiddlers were > never saved to disk: > > - the browser interface displayed no error whatsoever > - the icon that shows "Status of synchronization with the server" > displayed everything was fine, and lit up every time I edited or created a > new tiddler > - the error message printed by the tiddlywiki server only referred to > a specific tiddler, that I took care to copy somewhere else before > restarting the server > > To me it seems like I really had no way to know that restarting the > tiddlywiki server would have caused such a dramatic data loss. > Even if I had noticed earlier, was there any way to "force" the tiddlywiki > process to flush to disk all tiddlers that were created and that were in > the process' memory only? > > Any suggestion is appreciated, I like tiddlywiki but I need things to be > reliably synced to the disk that I back up nightly. > Cheers, > Enrico > -- 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/a8e726ea-cfb6-4fad-9ba4-2bac1466638bo%40googlegroups.com.
