couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patrick Barnes <>
Subject Re: CouchDB in multi-tenant environment
Date Wed, 09 Jun 2010 23:29:43 GMT
Another solution is to use couchapp - 'couchapp push' on an existing
database will only update the design doc. As part of the upgrade process,
you can just run push for each database.  This would be simple in an upgrade
script - it could even load the list of databases out of couchdb first.


On 10/06/2010 8:00 AM, "Vlad Mangeym" <> wrote:


I am evaluating CouchDB to be used in multi-tenant environment and
would like to know if there are ways to have design documents from one
database to be used by a  another database.

In other words, if we have client1, client2, client3 databases that
contain data (specific to a client) and application_code database that
has design documents (views, validation rules) that should be used by
all clients is there a way to point to the application_code db from
other client data databases?

Otherwise, it would be difficult to do application code upgrades: one
would need to replace design documents individually for each client...


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message