Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BD6BF9817 for ; Fri, 1 Mar 2013 09:39:51 +0000 (UTC) Received: (qmail 97704 invoked by uid 500); 1 Mar 2013 09:39:50 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 97211 invoked by uid 500); 1 Mar 2013 09:39:49 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 97188 invoked by uid 99); 1 Mar 2013 09:39:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Mar 2013 09:39:48 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.214.48] (HELO mail-bk0-f48.google.com) (209.85.214.48) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Mar 2013 09:39:41 +0000 Received: by mail-bk0-f48.google.com with SMTP id jf20so1246539bkc.21 for ; Fri, 01 Mar 2013 01:39:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=qOHMJIjKWsG3ULlJSn3PTOUl1/J/b93SZoZMa0vIE58=; b=D9aO1sXrv/74jt94+3AejQKBZcf30ZT6fjOZFW073RGisQ3wnxV9whOSK7ihEV84Mf zOXZUvdPeab75svEdaseqUW6HQoOh7hgh7K5HN77ovfmy9J1GYCT8eHH0uJnfChKlyS1 XCCeF8MjvodM69/6RvOQxx04ClF6KucZogKOtaDP1Nqa9i531auN1MWc1sKOgJ4K10iW HPhEc3HOtocwXWBibaHRBIW9qgBn55BiPFlQ1SpqlK9+G2/eR5lyfh7E3P9ex845k3u5 WofRO5lkijbqTMde68O80upqELaXJfN6vLFB2hQCqg6aUs3r35+KNdgQhi6RQPykOlt7 2rUQ== X-Received: by 10.204.9.4 with SMTP id j4mr3591277bkj.36.1362130760768; Fri, 01 Mar 2013 01:39:20 -0800 (PST) Received: from [192.168.2.100] (dslb-088-075-129-037.pools.arcor-ip.net. [88.75.129.37]) by mx.google.com with ESMTPS id r17sm2630979bkw.21.2013.03.01.01.39.18 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 01 Mar 2013 01:39:19 -0800 (PST) Message-ID: <51307792.1030708@netzmerk.com> Date: Fri, 01 Mar 2013 10:40:34 +0100 From: "Johannes J. Schmidt" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: user@couchdb.apache.org Subject: Re: Node + Couch References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQkUZ+NPDPmLIjgzqgZNOB4JMAmQrNTM0O58AI5qU7EylRncauAJ6TKMrXh6iPXt220Dg9Wx X-Virus-Checked: Checked by ClamAV on apache.org Thats awesome shit! Thanks! On 01/25/2013 06:17 PM, Ryan Ramage wrote: > 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! > > 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: > > https://github.com/garden20/gardener > > 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. > > 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. > > Optionally, it can be used to route http requests through couch (via > externals) to the node process. > > 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. > > So you know it is fairly young, so warnings apply. But it is in the process > of being used in a real product. > > Feedback welcome. > > Ryan >