jo / couch-daemon Goto Github PK

High-level os daemon API for CouchDB.

JavaScript 100.00%

couch-daemon's Introduction

jo

This is jo, a small utility to create JSON objects

$ jo -p name=jo n=17 parser=false
{
    "name": "jo",
    "n": 17,
    "parser": false
}

or arrays

$ seq 1 10 | jo -a
[1,2,3,4,5,6,7,8,9,10]

It has a manual, and you can read why I wrote jo.

Build from Release tarball

To build from a release you will need a C compiler to install from a source tarball which you download from the Releases page.

tar xvzf jo-1.3.tar.gz
cd jo-1.3
autoreconf -i
./configure
make check
make install

Build from Github

To install from the repository, you will need a C compiler as well as a relatively recent version of automake and autoconf.

git clone git://github.com/jpmens/jo.git
cd jo
autoreconf -i
./configure
make check
make install

Install

Homebrew

brew install jo

Ubuntu

apt-get install jo

Gentoo

emerge jo

Snap

Thanks to Roger Light, jo is available as a snap package. Use snap install jo from a Linux distro that supports snaps.

Windows

scoop install jo

Others

Credits

json.[ch] by 2011 Joseph A. Adams ([email protected]).

couch-daemon's People

Contributors

Stargazers

Watchers

Forkers

ejeklint sitewaerts

couch-daemon's Issues

Each db update triggers two changes events

Each update of a doc in a "followed" db creates two changes events which is a bummer. I guess this because the db first gets pushed to the dbs stream when daemon starts, and then again every time a 'changes' event is fired for that db.

I've tried to read code and figure out exactly what happens but it's difficult to follow the flow in all these streams and callbacks, so I need help figuring out the proper solution.

Newly created db's have empty opts needed for follow

support commonjs modules in filters

like couch does

Dynamically start watching new dbs matching whitelist

As far as I can see, new dbs matching the whitelist doesn't get added to couch-daemon, unless it's restarted.

log errors from filter functions

Extend the whitelist and blacklist option handling to accept regexps.

We can simply check for the presence of leading and trailing slashes, because a database name cannot start with a slash.
This way we can get rid of the two additional configuration options whitelist_regexp and blacklist_regexp

listen to db_updates

try to use follow.

Deleted db cause couch-daemon to crash

Tested with example "logger": delete a watched db and BOOM.

Stream API

The daemon should provide init, changes, configure and checkpoint streams, which can be chained to build a daemon instance.

think about configuration properties

maybe rename with stream type, eg dbs-blacklist

ignore 'compacted' events and others

https://github.com/jo/couch-daemon/blob/master/lib/dbs.js#L77 should be changed:

        if (change.type === 'deleted' || change.type === 'created')
          push(null, _.extend({ stream: 'dbs' }, change));

The change avoids unneccesary pushes.

We are running into serious problems with the following scenario: When a user logs in the first time, we create a user specific couch db and insert some design documents to that db. this is realized via a seperate node process with nano.

In this case, the couch-daemon (we use couchmagick) gets a massive bulk of events (creation of new db, updates for several design documents, etc.). I don't know why, but then the new db is not watched by couch-daemon, if if the dbs name is covered by the whitelist (/.*/ on our case).

Applying the above patch avoids the problem. I created a pull request: #17

Waiting for a follow release.
Then I'll update follow on nano.
Wait for nano release.
Update nano here.
Use nano's follow.
Remove the follow dependency.