Re: CouchDB - managing design documents?

To broaden this topic slightly, I'm thinking that some form of data migration automation would also be important to have, in addition to updating design documents. For example, if a document structure is modified, we would want to have an automated way of updating existing data to the new

Re: CouchDB - managing design documents?

Hi Tony, Thanks for the replies – we’ve also been looking at the various Couchapp implementations, but have been hesitant both for what you cite below (large additional stack of dependencies) and this part of the current CouchDB docs: http://docs.couchdb.org/en/2.1.0/ddocs/, which discourages

Re: CouchDB - managing design documents?

Hi, Alan: Thanks again for starting yet another interesting and important discussion. I've had to do a lot of this in my own work, and have alternated between: 1. Storing the design documents as raw JSON (mainly for testing). This is similar to the approach used in the example you

Re: Puppeteer - new headless Chrome library from Google

Hi, Alan. Thanks for pointing this out. The first and biggest question that has to be asked when considering something new, is "why should we use this?" First, why should we use this and not Testem/gpii-testem ? Testem already supports a range of browsers,