Scalable + Robust Storage Options (S3)

[Peter Green]

Hi there folks!

I'm new to the TiddlyWiki community, so apologies if I'm asking about something that's been discussed previously. I'm considering the use of TiddlyWiki for a project, which may end up being client-facing and so I'd like to be able to use S3 as a storage solution for the application.

I notice there's been some discussions around the use of S3 in the past, but I didn't see any solutions. Does anybody know of a plugin that would allow saving content to S3? I'm happy to look at implementing this myself, but I didn't want to duplicate any effort!

Thanks,

Pete

[Danielo Rodríguez]

The most similar thing I can think if is the couch adaptor .

[Jeremy Ruston]

Hi Peter

> Does anybody know of a plugin that would allow saving content to S3?

There's not an S3 adaptor at the moment, but it would make an excellent project to create one :)

A "sync adaptor" module in TiddlyWiki is responsible for synchronising changes to/from the local store to storage accessible via an asynchronous API. There's some documentation about them here:

http://tiddlywiki.com/dev/#SyncAdaptorModules

There are two sync adaptor plugins included in the main distribution:

* "filesystemadaptor.js" synchronises the serverside instance of TiddlyWiki with the file system, using standard Node.js async file APIs

* "tiddlywebadaptor.js" synchronises the browser instance of TiddlyWiki with the serverside using the TiddlyWeb HTTP API (which is also implemented in TiddlyWiki5)

The TiddlyWeb adaptor would be the best starting point for the S3 adaptor:

https://github.com/Jermolene/TiddlyWiki5/blob/master/plugins%2Ftiddlywiki%2Ftiddlyweb%2Ftiddlywebadaptor.js

The S3 API isn't a million miles from the TiddlyWeb API (assuming one was mapping tiddlers to S3 objects 1:1). A reasonable approach would be to store tiddlers in JSON and to use the S3 last modification date instead of TiddlyWeb's revision field.

The interesting thing about an S3 adaptor is that it could be run in the browser or on the server under Node.js. It's also possible to serve the TiddlyWiki HTML file itself from S3, of course, which might make authorisation easier to handle.

That should give you some pointers to get started, let me know if you have any questions,

Best wishes

Jeremy

On Tue, Dec 2, 2014 at 8:53 PM, Danielo Rodríguez <rdan...@gmail.com> wrote:

The most similar thing I can think if is the couch adaptor .

--
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

[Marica Odagaki]

I've put together a docker image for TiddlyWiki with s3fs support: https://github.com/ento/tiddlywiki-s3fs

Using s3fs means filesystemadaptor.js just works.

I'm running the image on AWS for my personal use. I haven't put much time and effort into writing a great readme file; happy to answer questions within my capacity.