Cheers Arlen. I'll check out PM2. I guess it would have been helpful if on of the Tiddlywiki NodeJS server docs (https://www.npmjs.com/package/tiddlywiki) had pointed to PM2 (or even forever as it does work when used correctly). Perhaps once I have found my way around the world of TW, I will contribute to the docs too.
Once again thanks for reviewing the issue. Andy On Saturday, May 9, 2020 at 11:17:38 PM UTC+1, Arlen Beiler wrote: > > 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 <an...@yogamatters.com > <javascript:>> 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 <arle...@gmail.com> 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 <an...@yogamatters.com> >>>> 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 10000 /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. <FX: SOUND OF HEAD BANGING ON TABLE> >>>>> >>>>> >>>>> 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 tiddl...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/tiddlywiki/af0978d5-310a-4094-b800-78e4267bace1%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/tiddlywiki/af0978d5-310a-4094-b800-78e4267bace1%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 tiddl...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywiki/d616fddc-2c8e-43d8-84fb-338acc809b0d%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tiddlywiki/d616fddc-2c8e-43d8-84fb-338acc809b0d%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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/3292ce50-1a07-493f-bbae-25807532b969%40googlegroups.com.
