couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benoit Chesneau <>
Subject Re: Part2: What's up dev? About couchapps.
Date Sat, 29 Sep 2012 07:16:01 GMT
On Fri, Sep 28, 2012 at 9:06 PM, Noah Slater <> wrote:
> +1 on what Dave said.
> Additionally, Benoit, can you remind me why RCouch has not been merged in.

It is using a build not based on autotools (only makefile) like
bigcouch. Also it was easier to hack on it instead of waiting for
feedback that was never coming . The first part of this thread explain

> And what are our current plans for it? And how does that play with the
> BigCouch merge that we have planned?

I want to merge it. The following question need to be solved:

How can I keep the ability to embed the couch core in others erlang
projects. Ie custom otp release and reuse parts of couch_core in
rcouch I need. I will post some possible directions about it in
another thread. I am still curious to know what are bigcouch plan on
that as well. This point is quite crucial for me. And as a side note
it explains why the development has forked here. The reactions on that
has always been biased.

Some other patches can be be extracted to be applied one by one to
couch. I can do that. But imo it would be better if we can solve the
point above first :)

- benoît

> On Wed, Sep 26, 2012 at 12:36 PM, Dave Cottlehuber <>wrote:
>> TL;DR +1 for including erica[1] into CouchDB proper.
>> To summarise a bit:
>> There are about 3 key things that all couchy tools do [1]….[5]:
>> - transform local js and erlang functions in separate files, into
>> design doc format
>> - include necessary libraries and attachments into those ddocs
>> - upload that ddoc into CouchDB
>> and optionally:
>> - support cloning ddocs (downloading and reversing the transformation)
>> - pushing arbitrary json docs with optional attachments
>> - pre/post hooks to minify, uglify, etc
>> - package mgmt
>> - keep some local state & store it in the ddoc to avoid unnecessary
>> transfer of attachments
>> We need to make the first steps when moving past using futon as easy
>> as possible, and consistent across platforms, with a minimal tooling
>> requirement. Node is awesome but is moving way too fast, and erlang is
>> the logical next choice.
>> If Benoit is willing, a slimmed down erica[1] code could be included
>> into CouchDB proper, or at least blessed as the canonical version.
>> It's in erlang, & with some rebar magic you have a stand-alone escript
>> that can be located anywhere in your path. The only additional code
>> I'd like to see is that it supports multiple ddocs, and handle
>> uploading normal docs as well as ddocs.
>> Personally, I only really understood ddocs after using CouchDB for
>> quite a while. I suspect I am not alone in this!
>> [1]:
>> [2]:
>> [3]:
>> [4]:
>> [5]:
>> A+
>> Dave
> --
> NS

View raw message