couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Ippolito (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1848) Multi replication UI in Fauxton for replicating a set of databases
Date Tue, 09 Jul 2013 04:45:57 GMT


Bob Ippolito commented on COUCHDB-1848:

I have a use case for this feature. My app creates
a database for each user. The rationale for this is simple: I'm using PouchDB on the client,
so the only reasonable thing to do in order to get bidirectional replication working without
leaking information to users that shouldn't see it is to structure it this way.

So, now I have N+1 (_user + len(_user)) databases to worry about, and I need to replicate
them from one Couch to another. My immediate need is that I'm teaching this class at a school
where internet is spotty, so we ended up using a Couch hosted on my laptop, and now I want
to dump it all into the central server (hosted at Iris Couch) for redundancy and so the students
can access their data off-site. In this particular case, today, N is 17 so it's doable by
hand or with a small script, but I don't think I'm the only one with this problem.
> Multi replication UI in Fauxton for replicating a set of databases
> ------------------------------------------------------------------
>                 Key: COUCHDB-1848
>                 URL:
>             Project: CouchDB
>          Issue Type: New Feature
>          Components: Fauxton
>            Reporter: Russell Branca
> Sometimes you want to be able to replicate a set of local databases to a remote server,
or vice versa. A simple approach would be to allow the user to select a list of databases,
and then specify a remote database to replicate to.
> Another nice feature would be to support the inverse, where you can specify a remote
CouchDB to open, select the list of databases you're interested in, and then replicate those
all locally.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message