Currently the api for couchdb-push requires a path to a couchapp directory or json. In my use case I already have the json in the app logic and do not want to create a temporary file from it.

Currently, travis is testing node 0.10, 0.12, iojs, etc.

And we're not testing anything beyond node 4.0 but 6.0 is LTS now.

Hi,

I like to use your module for my ember-cli-deploy-couchdb and it works on my localhost but I have some async issue. In

https://github.com/broerse/ember-cli-deploy-couchdb/blob/master/index.js

the couchapp is never upload to cloudant because the deploy does not wait for the push. The this.log is never printed. On localhost it is faster and than it works.

How do I wait? I am new to nodejs so I hope you can give me some pointers.

Whenever I use couchdb-push for a url with basic auth , I get an ENOENT error

$>> couchdb-push http://admin:password@localhost:5984/pop --index

    { [Error: ENOENT, stat '/home/deepster/POP/couchdb/http:/admin:password@localhost:5984/pop']
      errno: 34,
      code: 'ENOENT',
      path: '/home/deepster/POP/couchdb/http:/admin:password@localhost:5984/pop' }

When I use couchdb-push on a fresh couchdb installation, without any admins setup, It works fine

I am trying to use this through the command line on Windows. Is that possible ? If yes, what is the install procedure ?

Thank you for your help.

When simultanously push docs to the same db that previously did not exist an error is returned:

{ error: 'file_exists',
  reason: 'The database could not be created, the file already exists.' }

See https://github.com/jo/couch-push/blob/master/index.js#L119

to be consisten across the other projects this should be called couchdb-push

replication documents also (like user docs) have some fields updated by couchdb. These fields should be considered when diffing.

user docs needs to be diffed specially, because the salt gets inserted server side.

Right now, if I give couchdb-push an URL like http://localhost:5984/mail/bigbluehat-com/byoung it throws the following error:

...\node_modules\couchdb-push\node_modules\couchdb-ensure\index.js:12
  couch.request({
        ^
TypeError: undefined is not a function

If I escape them, however, things work as they should: http://localhost:5984/mail%2Fbigbluehat-com%2Fbyoung

Obviously the escaped version is what CouchDB actually wants, but it'd be nice for the developer to not have to care that much--or go figure out what's needed from that error.

Having this as part of the library would save a bunch of URL parsing boilerplate in other people's code too, fwiw.

Thanks!

once apache/nano#222 is in

Have a watch option which pusheds everytime a file is changed, similar to watchify.

See https://github.com/eHealthAfrica/couchdb-bootstrap/issues/7

how i know from couchdb-bootstrap if i create or already exists ?

https://github.com/eHealthAfrica/couchdb-ensure/blob/a2bdeb09f8a766b722ab0565fd3409e7104cfb7c/index.js#L21

take a look

I'd like to use couchdb's internal support for CommonJS modules. I'd think I'd be able to create my design document like this:

module.exports = {
  _id: "_design/app",
  language: "javascript",
  views: {
    lib: {
      requireField: function(doc, fieldName){
         if (!doc.hasOwnProperty(fieldName)){
           throw({forbidden: "missing field: " + fieldName});
         }
      }
    }
  },
  validate_doc_update: function(newDoc, oldDoc, userCtx){
    var requireField = require("views/lib/requireField");
    requireField(newDoc);
  }
};

When couch-push compiles my commonjs code, it converts the requireField function to a string as expected for a view, but in this case, we'd need a module.exports = prepended to that string, so that requireField actually exports something.

I don't see an obvious way to make this work without a pull request, but I figured I'd ask before I start thinking about a potential solution.

First, thanks for building this! 😄

Second, it'd be great to mimic the couchapp.py behavior (and erica also, iirc), such the doc._id can be calculated out of the current file or directory name--if it's missing in the JSON or as an _id file.

Without that, there's a migration process needed when moving between CouchApp tools--which would be great to avoid.

Thanks again!

Use multipart request for that purpose.

Hello,
I would like to use the https connection (on port:443), but I receive the
{message: 'error happened in your connection', scope: 'socket', errid: 'request'}
Error.
Is there somethin I have to consider for https and different ports?
Kind regards
Oliver

CouchDB Push always overwrites existing files. We maybe need to support a hook, which can be supported as an option when using the API and will handle a merge:

{
  merge: function(newDoc, oldDoc) {
    newDoc.something = oldDoc.something
    return newDoc
  }
}

Sometimes its more convenient to group documents as one JSON file in bulk docs format, e.g.:

{
  "docs": [
    {
      "_id": "london",
      "name": "London"
    },
    {
      "_id": "berlin",
      "name": "Berlin"
    }
  ]
}

Currently couchdb-{compile,push} operate at a per-document level, which can become unwieldy in some scenarios, for example DB seeding.