Thanks for the reply, And secure_rewrites=false doesn't circumvent any of the other security mechanisms in couch, specifically user access to a database?
Also, (more of a couchapp philosophy question here) if I'm starting to use a second database, am I still writing a couchapp? Sure I'm using the couchapp tool, but doesn't this go against the philosophy of couchapps? Will I encounter scalability problems trying to force a complicated webapp into the couchapp model? --Jonathan On Fri, Jul 8, 2011 at 9:34 AM, Benoit Chesneau <[email protected]> wrote: > On Fri, Jul 8, 2011 at 5:30 PM, Jonathan Geddes > <[email protected]> wrote: > > CouchDB users, > > > > I'm working on a couchapp, and up untill now, a single rewriter on a > single > > database, coupled with a vhost has been all I need. > > > > However, as the complexity of the app grows, I'm starting to need > additional > > databases. Now I need a rewriter that spans multiple databases... > > > > Is there a good way to do this within couchdb? I suppose I could set up > > multiple vhosts, but that's not optimal. Can a rewriter in one database > > point to end points in another database somehow? > > > > Yes, it's possible. > > you have to set secure_rewrites to false in the settings and then you > can use relative paths to go in other db: > > > { > "from": "/some/path", > "to":"../../../somedb" > } > > > - benoît >
