Thanks Kevin. For the meantime I'll probably rely on batch files / task scheduler to do this.
I am hopeful that since variants like TiddlyDesktop were able to include auto-backup per change with revisions, that someday MultiUser might gain that capability - though maybe structurally they're too dissimilar. On Friday, May 11, 2018 at 8:06:16 AM UTC-4, Kevin Kleinfelter wrote: > > Backups are a concern for me too. Since it is the node.js version, every > tiddler is in the file system. Right now, I'm vacillating between three > options: > > - A shell script (or batch file) which runs as a scheduled task to zip > up the tiddler folder. In an unrelated project, I use such a script to > backup to %Weekday%.zip and to %Hour%.zip. The script runs hourly. It > doesn't overwrite %Weekday%.zip until it becomes a week old. That way, I > have a backup each hour for the current day and each day for the current > week. > - git, with hourly commits. git works pretty well for this except > that locating the right commit to revert is awfully geeky. You can just > commit hourly and git will notice that nothing changed (if nothing > changed) > and not make a new backup. > - I've got a Mac, but it isn't where I run my wikis. I could just > replicate the tiddler folder with rsync to my Mac and let Time Machine > handle the backups. > > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/fe0e0023-6827-4d62-92ff-8c18d9e6deed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
