Schmidt
Schmidt
I see.
This is an interesting issue. Will investigate. This might be a bug in nano, but https://github.com/dscape/nano/issues/278 is a different one.
Seems like this is not nanos problem
`db.config` does not get the initial config but is only a stub with `url` and `db`, see here: https://github.com/dscape/nano/blob/master/lib/nano.js#L693 Nonetheless the config should be used like tested here: https://github.com/dscape/nano/issues/296
Currently only auth urls are supported for the CLI. For api usage you can pass in [everything nano acceps](https://github.com/dscape/nano#configuration). Here you can pass [`requestDefaults` with an `auth` object](https://github.com/request/request#http-authentication). For example:...
Could you please paste the contents of the files here, so that I can reproduce the issue?
Totally see you point, thanks for the explanation.
Also described here: https://github.com/eHealthAfrica/couchdb-best-practices#modularize-view-code
This is because of the `\r`
Looking at the [code of v4.1.1](https://github.com/dscape/nano/releases/tag/4.1.0) (and also [v4.0.0](https://github.com/dscape/nano/releases/tag/4.0.0)) Nano has even then used the `_replicate` endpoint, not the `_replicator` database: ``` js return relax({db: "_replicate", body: opts, method: "POST"},...