Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of bchesneau@gmail.com
 designates 209.85.214.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAFnw-00YMLYo4tZY0yHM-OCHrvqnnOMbH05Y861_QRJ5hR0wjQ@mail.gmail.com>
References: 
 <CAFnw-00YMLYo4tZY0yHM-OCHrvqnnOMbH05Y861_QRJ5hR0wjQ@mail.gmail.com>
Date: Fri, 8 Jul 2011 17:34:48 +0200
Message-ID: 
 <CAJNb-9qdHRYK3fodi+rQ0bo4XHcehMQE2yMFm0JHNk99o=woCQ@mail.gmail.com>
Subject: Re: global rewriter
From: Benoit Chesneau <bchesneau@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Jul 8, 2011 at 5:30 PM, Jonathan Geddes
<geddes.jonathan@gmail.com> wrote:
> CouchDB users,
>
> I'm working on a couchapp, and up untill now, a single rewriter on a sing=
le
> database, coupled with a vhost has been all I need.
>
> However, as the complexity of the app grows, I'm starting to need additio=
nal
> 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=EEt