That is a very interesting setup, thank you for taking the time to share it.

My use case for notes also involves interacting with them via text editors 
and other tools as well as  having them in TiddlyWiki. What I set up a few 
years back was a combo of fswatch + cURL + the tiddlywiki server API. 
Watching for file system changes wasn't as reliable at the time so the 
setup was a bit finicky and tricky to get it right. So I've never fiddled 
with the config or even upgraded the wiki once I had it working.

The next version of TW includes a server sent events feature with which 
tiddlers propagate from the server to client almost instantly, so that will 
be my queue to upgrade that wiki. I will need to consider if moving to 
nodemon might make sense as well, I use it for TW dev at the moment and it 
does seem to work well enough.

Cheers,
Saq 

On Sunday, July 4, 2021 at 3:27:35 PM UTC+2 [email protected] wrote:

> I hesitate slightly in posting to this group as my use case covers such a 
> niche audience, I'm not sure how much utility there is in sharing it.  
> However in short I wanted to host a TiddlyWiki on a Raspberry Pi, create 
> tiddlers from the command line and edit them with vim.  Once I figured out 
> how to do that I thought I'd blog about it (mostly so I can retrace my 
> steps later on):
>
> https://www.preciouschicken.com/blog/posts/tiddlywiki5-raspberry-pi-guide/
>
> I'm not sure the nodemon hack will be required in future, I think I read 
> another thread suggesting that this form of updating functionality might be 
> built in (though I could have got that wrong)?
>
> Many thanks to the creator and the maintainers of TiddlyWiki.  Really 
> enjoy using and playing around with it.
>

-- 
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/c8b8fbff-198c-49b9-b82f-2714b01ab274n%40googlegroups.com.

Reply via email to