Hey! Another thing you may want to try is my project
https://github.com/redgeoff/replicate-couchdb-cluster as it also replicates
the security objects.
On Mon, Oct 1, 2018 at 5:39 AM Peter J Krawetzky <[email protected]>
wrote:

> So you just hit the very same issue I had which forced me to come up
> with my own process.  I have opened a ticket with apache for this very
> issue.
>
> https://github.com/apache/couchdb/issues/1604
>
> What I ended up doing is extracting the permissions from each database
> to a file and then reapplied the permissions to each database once
> couchup was executed.
>
> Export:
> curl -X GET http://localhost:5984/{dbname}/_security > {dbname}.json
>
> import:
> curl -X PUT http://localhost:5984/{dbname}/_security -d {dbname}.json -H
> "content-type:application/json"
>
> Good luck.
>
> ------ Original Message ------
> From: "Andrea Brancatelli" <[email protected]>
> To: [email protected]
> Sent: 10/1/2018 7:13:31 AM
> Subject: CouchDB 1.x to CouchDB 2.x
>
> >Hello everybody.
> >
> >Today I upgraded the first CouchDB 1.7 to CouchDB 2.2 in production
> >with
> >the help of the marvellous couchup, by just coping the old .couch files
> >in the new locations.
> >
> >Everything went smoothly apart from some points:
> >
> >       * The Documentation doesn't mention the need for the -i switch when
> >invoking couchup to migrate the _users and _replication databases.
> >Maybe
> >a note on this would be useful in scenarios when one is migrating an
> >entire machine.
> >       * I had to manually reapply all the permission on the databases.
> Seems
> >a quite obvious conseguence of the replication-process not replicating
> >the security document. Yet I don't think that replicating a server into
> >a totally open one makes a lot of sense. Did I miss something?
> >
> >Since I have to do a couple more Production servers with more complex
> >permissions, do you have any brilliant suggestions on how to replicate
> >permissions too?
> >
> >Quite frankly it sounds like an easy improvement to couchup as well,
> >but
> >personally I'm a bit python-adverse eheheh
> >
> >Thanks
> >
> >--
> >
> >Andrea Brancatelli
>
>

Reply via email to