Hi, Thanks both.
Yes, I'm running the couchadaptor, which as Mario points out means I don't need a separate app server. However, I'm keen on the use case where the database is separate to the app, so I've pursued this route. I hadn't realised that the couchadaptor was entirely client-side, I had assumed there was a server-side component. So I've adjusted the couchadaptor to work with cross-domain requests to CouchDB, and this is working nicely. I have an app running on heroku that is syncing to a couchdb on iriscouch. This feels very exploratory, so I've opened a pull request[1] with my changes to the couchadaptor to add context to the discussion[2] around that. Cheers, J. [1] https://github.com/wshallum/couchadaptor/pull/2 [2] https://github.com/wshallum/couchadaptor/issues/1 On Thursday, October 9, 2014 8:49:25 PM UTC+1, PMario wrote: > > On Thursday, October 9, 2014 9:09:21 PM UTC+2, jayfresh wrote: >> >> I've had a go setting up the couchadaptor. It's fine getting it running >> on a cloud CouchDB database (IrisCouch in my case), but it's not clear how >> to get the couchadaptor in the heroku TW5 to handle tiddler saves and push >> them off to the other database. >> > > You can use couchdb to serve the whole TW app. So there is no need to > combine it with heroku. It's just more moving parts. > -m > -- 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.
