Replicate to remote CouchDB

Hi, I’ve been struggling since some days to replicate data to a remote couchDB after I’ve encrypted my local Pouch with crypto-pouch.

First I thought it was not working because I was using a filter, as mentioned in issue 37. I removed the filter and still couldn’t make it work.

After testing, I could finally achieve replication after applying the crypto function to my remote database as well, using the same password.

If that’s the way it works, could you please make it more clear in your documentation?

Then, I noticed that this way, the data in my remote Couch were been inserted encrypted after the replication.

Is there a way to keep encrypted data on the client, but sent it unencrypted to the remote DB?

Many thanks in advance.

[tarazhong]

Hi, we had the same issue when encrypting a local PouchDB that was sync with a remote url :

Original code

this.localdb = new PouchDB('database');
this.localdb.crypto('password');
var remoteURL = 'http://127.0.0.1:5984/database'
let options = { .... }
this.localdb.sync(remoteURL, options)

What we did to solve this issue was to create 2 DBs, one encrypted DB that replicates data from Couchdb into a local Pouchdb (pull changes). One not encrypted remote DB but with no data stored that will push changes.

Adapted code

this.localdb = new PouchDB('database');
this.localdb.crypto('password');
var remoteURL = 'http://127.0.0.1:5984/database';
let options = { .... }
this.localdb.replicate.from(remoteURL, options);
this.remoteDB = new PouchDB(remoteURL, options);

All get/query requests are done with the localdb and all put/post requests are done with remoteDB.

Also we had to modify crypto pouch index.js file, to add ‘_revisions’ to ignore variable (line 18 var ignore = [‘_id’, ‘_rev’, ‘_deleted’,‘_revisions’]) otherwise localDB will not handle pull changes.

[jackkleeman]

I have a solution for this; have two pouchdb instances, one with crypto pouch loaded as a plugin, one without. Do all your document manipulation in your crypto instance, but setup replication in your blank instance. It’s a little hacky, but was a 2-3 line change for me that works out the box. Data is sent to the server encrypted, and you could then set up the couch server to be able to decrypt given the same password.

I am using this for a zero knowledge application where the server doesn’t have access to any user data, its just a dumb store.