Hi Hans, > 1. a local copy > 2. a web copy (preferably self-hosted but not necessary) > 3. keeping 1&2 in sync
I agree that this is a very attractive configuration. In TWC we handled 3 by opening the local copy (as a file:// URI) and then syncing up to the server. Recent changes to browser security settings means that that doesn't work anymore. For TW5 we'll have to handle it by opening the online web copy and importing the local wiki file. That can be done at the moment. I do plan to add visual diffs to the import dialogue to make it easier to triage changes when syncing. I'm actually interested in a three-way configuration: 1. A local copy of the wiki that I edit via a file:// URI (and sync with Dropbox) 2. An online dynamic web copy that runs under Node.js 3. An online static web copy that is just a bunch of files generated under Node.js and uploaded to a static host like Amazon S3 (1) would be for me to work on privately, (2) would open up the possibility of working with a team and (3) would be the means for publishing read-only content (the vast majority of visitors to a blog, for example). TW5 can already generate static HTML copies of wikis, we just need a mechanism under Node.js to periodically update the static renderings and upload them to storage. Best wishes Jeremy On Sat, Oct 11, 2014 at 1:03 AM, Richard Smith < [email protected]> wrote: > Hi Hans, > > I'm no expert at all but have been playing with different set-ups. > > Hosting your tiddlywiki as a website is spectacularly easy. If you have a > Dropbox public folder or similar, you can put your tw in there, point a URL > at it and you've got a website. (I have a demonstration of this at > www.didaxy.net). Editing and saving the tiddlywiki then updates the > website (I was truly astonished at how quickly this happens) > > One of my next projects is to figure out how to do the same using github, > which I believe is how Jeremy hosts tiddlywiki.com. > > If you want to edit your tw on the web and/or have multiple users then it > gets a bit trickier - not because you can't do it, I think, but because > there are many possible ways and you must choose the right one for your > use-case. > > The big problem with multi-user is how to handle edit-conflicts, I think, > and there are several discussions of the topic in the forum, eg: > https://groups.google.com/forum/#!searchin/tiddlywiki/edit$20conflict%7Csort:date/tiddlywiki/8NdvFoz-GCI/H0yWp6NxZSYJ > > Do you know about Tiddlyweb and the other back-ends such as Tank? > > Regards, > Richard` > > -- > 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 http://groups.google.com/group/tiddlywiki. > For more options, visit https://groups.google.com/d/optout. > -- Jeremy Ruston mailto:[email protected] -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
