I had a similar issue when i used Nativefier ( https://github.com/jiahaog/nativefier) to create a standalone desktop app. I was trying to create an app from a TW that was online. Luckily I noticed that the saves were not stored when I closed the app.
20:48, 29th June 2020: Update: This approach has some issues. When the app is reopened after closing, the data is lost. Not sure where the problem is. Is it due to the save plugin or issue with data storage. I stopped using the app-ified wiki till i figure it out. I use either Firefox or Chrome to use the worklog. I discovered Nativefier <https://github.com/jiahaog/nativefier/>, a command-line tool to easily create a desktop application for any web site using Electron. I ran that tool to generate a Windows app. I also picked up an worklog icon <https://www.iconfinder.com/iconsets/work-from-home-18> from Iconfinder to make it more app-like.~ Though I am not sure if this is related to the issue that you had mentioned. I just hope some tries this and figures out the reason. I then switched over to TIddlyDesktop and moved my worklog offfline. Regrads, Xavier On Sunday, 28 June 2020 18:17:44 UTC+5:30, 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/ffd9d8cb-718a-4568-b4b4-3d61f1a9a332o%40googlegroups.com.
