Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of snbartell@gmail.com designates
 209.85.160.42 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Node + Couch
From: Stephen Bartell <snbartell@gmail.com>
In-Reply-To: 
 <CAL-h1aRaoqKf5zuvrN9H7h2SgF6MCJFS2jCSur9Bjxco5DqywQ@mail.gmail.com>
Date: Thu, 28 Feb 2013 14:40:55 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <8171B4C3-426F-406E-971D-E66DCBF79BF4@gmail.com>
References: 
 <CAL-h1aRSG2gOK9SNLiCQ=Mf+Ok9RDc19dsAQ56bEjPZdT56Efg@mail.gmail.com>
 <CAPaJBx7CQBXdLmW9fM_eb619XLpG0m36FdoZsxGfdLMcy7HmRQ@mail.gmail.com>
 <-3357587684347326953@unknownmsgid>
 <CAL-h1aRaoqKf5zuvrN9H7h2SgF6MCJFS2jCSur9Bjxco5DqywQ@mail.gmail.com>
To: user@couchdb.apache.org

+1 Im stoked about this.  At my day job we've done something similar, =
and its been a game changer in what/how we deploy for customers.  I hope =
to see the garden grow ;)
On Feb 28, 2013, at 2:28 PM, Ryan Ramage <ryan.ramage@gmail.com> wrote:

> It will work on both. The idea is you can run the node processes =
anywhere
> you want.
>=20
> The gardener has an optional http proxy thing to your node process, =
which
> probably wont work with cloudant or iriscouch because they have =
disabled
> the couch_httpd_proxy setting.
>=20
>=20
>=20
> On Thu, Feb 28, 2013 at 3:14 PM, Lance Carlson =
<lancecarlson@gmail.com>wrote:
>=20
>> This is very cool indeed. Do you know if this will work on cloudant =
or
>> iris? Or are you supposed to run node on a remote server like on
>> Heroku?
>>=20
>> Sent from my iPhone
>>=20
>> On Feb 28, 2013, at 4:05 PM, Noah Slater <nslater@apache.org> wrote:
>>=20
>>> Hey, this sounds really cool Ryan!
>>>=20
>>>=20
>>> On 25 January 2013 17:17, Ryan Ramage <ryan.ramage@gmail.com> wrote:
>>>=20
>>>> Hey all, there are many out there who use couchdb + node together. =
And a
>>>> lot are excited about Jason Smith's (and others) work using node as =
a
>> view
>>>> server. I say the more options the better!
>>>>=20
>>>> I just wanted to let others know of another experiment of mixing =
node
>> and
>>>> with couch. It's called gardener and the repo is here:
>>>>=20
>>>> https://github.com/garden20/gardener
>>>>=20
>>>> The premise is based around keeping a node module bundled with a =
design
>> doc
>>>> (or a couchapp).
>>>> Why? Maybe your ddoc map/reduces twitter feeds and you want to have =
node
>>>> fetch and store from twitter. Lots of imaginary scenarios.
>>>>=20
>>>> The gardener is a node process watches a couch, looking for design =
docs
>>>> with a node module attached. Finding one, it will simple npm =
install it,
>>>> spawn a forever process, and pass it the db url to connect to.
>>>>=20
>>>> Optionally, it can be used to route http requests through couch =
(via
>>>> externals) to the node process.
>>>>=20
>>>> The idea here is to build reusable backend node processes that work =
well
>>>> with couch, or a mechanism to distribute slightly more powerful
>> couchapps.
>>>> And this all works with couch today.
>>>>=20
>>>> So you know it is fairly young, so warnings apply. But it is in the
>> process
>>>> of being used in a real product.
>>>>=20
>>>> Feedback welcome.
>>>>=20
>>>> Ryan
>>>=20
>>>=20
>>>=20
>>> --
>>> NS
>>=20