Oh, and note that for 3.2.0 and CouchApps to work, you will have to change the 
default CSP headers: https://docs.couchdb.org/en/stable/cve/2021-38295.html / 
https://github.com/apache/couchdb/pull/3724

Best
Jan
—
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/

*24/7 Observation for your CouchDB Instances:
https://opservatory.app

> On 20. Oct 2021, at 14:56, Miroslav Rodic <rod...@arco011.com> wrote:
> 
> For an application, developed 10 years ago as couchapp with CouchDB 1.1.1, an 
> OFF-LINE data exchange (synchronization) is implemented by adding the local 
> .couch file, with randomly generated name, in a .zip file, which is then 
> sent, by email, to another user and then that user extracts and copies the 
> received .couch file into the local CouchDB instance. The imported .couch 
> file is then synchronized with the appropriate local database using 
> replication. All export/import steps, including the final replication, were 
> implemented within the application, so there were no problems with non-IT 
> users understanding how to use it. Since the application is implemented as a 
> couchapp type, the necessary Erlang functions have been developed that allow 
> archiving/copying/etc.
> 
> The question follows: is it possible to keep the same approach in off-line 
> synchronization with the latest version of CouchDB, which is 3.2.0, when the 
> installed CouchDB is configured as a single node? If this is not possible, 
> then which solutions are recommended for off-line synchronization?
> 
> Copying of .couch files is not clearly explained in the backup documentation. 
> A backup assumes, if I understood correctly, that .couch files can be copied 
> to a secure location, and then, when needed, can be restored by overwriting 
> the existing .couch files in the data directory. If, for any reason, the 
> corresponding DB is deleted by using the Fauxton before the .couch files are 
> reverted back, then reverted .couch files will not be accepted and displayed 
> in Fauxton. This is the behavior I had on my comp testing the backup/restore 
> procedure.
> 
> Backup/restore procedure tested on OS X 10.15.7 with CouchDB 3.2.0, where 
> path to data directory is as follows: ~/Library/Application 
> Support/CouchDB2/var/lib/couchdb.
> 
> Regards,
> Miroslav
> 

Reply via email to