Configuration for Autosave, node.js, Dropbox, Windows, Linux, OSX

[Matthew Petty]

I wanted some advice on how to set up my Tiddlywiki to be the most efficient and safe.

I want to access it from multiple machines via Dropbox. My work machine is a Windows laptop. My personal laptop runs Ubuntu Linux. It would be great if my wife could access it on he Macbook.

I have TW5.07-beta in Dropbox at the moment, and I use Firefox with the TiddlyFox extension to edit and save it. I do this at home and at work. It works fine, and I love the flexibility of filters and tags. Very powerful.

Is there a way I could set it up so that I could have real Autosave? There have been times I've forgotten to click save, and I've lost stuff as a result. I see that node.js could be a solution, but I don't know how to proceed.

Could someone suggest a configuration that would work on the three types of machines, and give autosave capability, and whatever other cool tricks node.js can give?

More critically, could someone write or point to a step-by-step tutorial to set all this up?

Thanks for any suggestions and help,

Matthew

[Matabele]

Hi

TiddlyDesktop (https://github.com/Jermolene/TiddlyDesktop) provides autosave with a standalone TW5 file without the need to set up node.js -- I have this running on my Linux os and on my wife's Windoze7 os. A copy of a TW5 file in a Dropbox folder can, therefore, be used on multiple devices -- but not at the same time!

An alternative is to use a node.js version on your Linux os, then export an offline version to Dropbox periodically. This offline file can be edited on other devices with TiddlyDesktop, then re-imported back into node.js when returning to your Linux os.

One trick to minimise the sync problem with a shared TW file in a Dropbox folder, is to edit tiddlers in another TW located in a normal folder. Drop the tiddler to edit onto your normal TW file (or create a new one), edit it, then drop the finished tiddler back onto the shared TW file in Dropbox when done.

regards

[Danielo Rodríguez]

Matabelle that sounds really complicated.

One question : is your periodical export automated? Since node.js version knows when you save a tiddler I think should be easy to have a real time updated exported version.

[Jeremy Ruston]

Hi Matthew

Autosave is supported in TiddlyDesktop and with TiddlyFox; you just need to upgrade to the latest TW core version to get it.

Best wishes

Jeremy

--
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+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

--
Jeremy Ruston
mailto:jeremy...@gmail.com

[Matabele]

Hi Danielo

No - I think autosave to Dropbox is unnecessary. I work on a node.js, then export an offline copy to Dropbox when done (this functions as a backup.) Individual tiddlers can be dropped onto an open offline copy in TiddlyDesktop, but I don't find myself doing this very often.

For an automated solution, I would consider using git and a Github repo of the node.js directory itself (this would avoid the necessity of uploading the entire TW.) This scheme would also provide a mechanism to sync a TW between two users working on the same TW.

regards

[Danielo Rodríguez]

Hello Matabelle

I tried with git, but I don't get any automatic track of changes. The main problem is that git does not track new files automatically, so I have to run git add every time I create a tiddler. Even if I use git add *.tid. How did you do it?

I don't want to manually backup a standalone version to Dropbox. What I want is node doing it automatically on every edit. Maybe a bit overload but I think my computer can take care of it. Do you know hot to accomplish this?

[Matabele]

Hi Danielo

I was thinking more along the lines of a cron job -- saving periodically. I suppose it must be possible to get the tracking across from node.js to git via a script, but have never attempted this. 

The other option is to use tiddlywiki node.js commands to save the node.js version to Dropbox -- again I haven't attempted this as yet.

regards

[Matthew Petty]

I have updated to 5.0.12-beta, and the autosave now works. That's great!

For now, then, I will stick with it as it is.

Thanks for your help,

Matthew

website: matthewpetty.com

podcast: coiledspring.org

READ CAREFULLY. By reading this email, you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies ("BOGUS AGREEMENTS") that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.

--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/nP0pGhkOtJY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.