+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 <[email protected]> wrote:
> It will work on both. The idea is you can run the node processes anywhere > you want. > > 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. > > > > On Thu, Feb 28, 2013 at 3:14 PM, Lance Carlson <[email protected]>wrote: > >> 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? >> >> Sent from my iPhone >> >> On Feb 28, 2013, at 4:05 PM, Noah Slater <[email protected]> wrote: >> >>> Hey, this sounds really cool Ryan! >>> >>> >>> On 25 January 2013 17:17, Ryan Ramage <[email protected]> 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 >>> >>> >>> >>> -- >>> NS >>
