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 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.

Reply via email to