sync tiddlywiki accross machines

683 views
Skip to first unread message

Maaaaaaaaaaaaaaartin

unread,
Oct 22, 2016, 5:00:37 AM10/22/16
to TiddlyWiki
Dear all:

I thought my setup was pretty solid: I run tiddlywiki using nodejs on multiple linux (and one macos) desktop/laptop and an android phone; the TiddlyWiki folder being synchronized using DropBox. However I am getting multiple issues:
 - When switching from one device to the other (note that most devices stay up even when I'm working on another one), I often need to restart the nodejs server, otherwise it does not seem to be seeing the changes that DropBox pushed to the folder in the mean time;
 - In the tiddlers folder, many files seem to have many versions, .tid, .tid.tid, .tid.tid.tid, .tid.tid.tid.tid, .tid.tid.tid.tid.tid, …;
 - When switching from one device to the other I often get multiple draft versions of non-draft tiddlers, multiple draft versions of deleted tiddlers, deleted tags, …
How can I strengthen my setup? What is the best way to sync a nodejs tiddlywiki across multiple devices? Thanks!

Martin

Tobias Beer

unread,
Oct 22, 2016, 6:25:00 AM10/22/16
to TiddlyWiki
Hi Martin,
 
 - When switching from one device to the other (note that most devices stay up even when I'm working on another one), I often need to restart the nodejs server, otherwise it does not seem to be seeing the changes that DropBox pushed to the folder in the mean time;

That is how the server works atm, I believe. If you make local changes, you need to restart the server for them to be available in a rendered wiki (elsewhere). I think this is so, since the sync issues that otherwise need to be overcome are quite significant.

 - In the tiddlers folder, many files seem to have many versions, .tid, .tid.tid, .tid.tid.tid, .tid.tid.tid.tid, .tid.tid.tid.tid.tid, …

That's a bug being fixed with the next version

Best wishes,

Tobias.

Maaaaaaaaaaaaaaartin

unread,
Oct 23, 2016, 3:16:32 AM10/23/16
to TiddlyWiki
Thanks Tobias!


 
 - When switching from one device to the other (note that most devices stay up even when I'm working on another one), I often need to restart the nodejs server, otherwise it does not seem to be seeing the changes that DropBox pushed to the folder in the mean time;

That is how the server works atm, I believe. If you make local changes, you need to restart the server for them to be available in a rendered wiki (elsewhere). I think this is so, since the sync issues that otherwise need to be overcome are quite significant.

I see. That's too bad but I guess I can live with that.


 - In the tiddlers folder, many files seem to have many versions, .tid, .tid.tid, .tid.tid.tid, .tid.tid.tid.tid, .tid.tid.tid.tid.tid, …

That's a bug being fixed with the next version

OK thanks. By the way, is there a way to follow the versions of TW, l Iike a specific ML or RSS? I guess this ML has that, but also a lot of other info so it is a little overwhelming.

Anyway, thanks again!

Martin

FBachofner

unread,
Oct 27, 2016, 6:50:35 PM10/27/16
to TiddlyWiki
Hi Martin:



On Sunday, October 23, 2016 at 12:16:32 AM UTC-7, Maaaaaaaaaaaaaaartin wrote:
OK thanks. By the way, is there a way to follow the versions of TW, l Iike a specific ML or RSS? I guess this ML has that, but also a lot of other info so it is a little overwhelming.

If you don't want to be overwhelmed, look at http://tiddlywiki.com/prerelease/  from time to time.  I just found out about it a few days ago and (assuming Jeremy keeps TW beta information up to date at that same address)  it's very easy to parse.

At least with the current prerelease (5.1.14-prerelease) the version # is clearly listed just beneath the TW Subtitle.

And you've got a pretty comprehensive listing of new features and fixes -- in the TW format with which you are familiar!  ;-)

Oh, and (quite reasonably) the linked version of TW within that TW is the prerelease version being discussed.

Tristan Kohl

unread,
Nov 3, 2016, 7:18:00 PM11/3/16
to TiddlyWiki
Hi Martin,


 - When switching from one device to the other (note that most devices stay up even when I'm working on another one), I often need to restart the nodejs server, otherwise it does not seem to be seeing the changes that DropBox pushed to the folder in the mean time;

Regarding your (manual) server restart you could use the node supervisor module. I know, it is intended for development but it should work pretty well with changing files due to DropBox syncs.

Cheers
Tristan
Reply all
Reply to author
Forward
0 new messages