Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of bchesneau@gmail.com designates
 209.85.215.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGt9U8jSxVu2=7wqRKA+gJt-Q5C27_oWh8zWYsLdgiAxfGnLwA@mail.gmail.com>
References: 
 <CAJNb-9p5+oWTqMrYXwvkHyFnuHn-Fg_RNHyLAexuX7LcNMV-gg@mail.gmail.com>
	<D9235C8A8D2B42C7B042ABBB28080C4A@cloudant.com>
	<CA+Y+444P9u73tuWJjx34R1uYb7bcW0DWAhGfGjBEiAUrms9hTQ@mail.gmail.com>
	<CA+Y+444AUL4a4pettPeByvsM+oUQRCNzzSWczC5sXSRVBVm7zA@mail.gmail.com>
	<5060B9C0.7010903@gmail.com>
	<CAL-h1aSJggTYY7HQZUBfktqUj1FD=TNdj7Tye5ECsyh0vdr1SA@mail.gmail.com>
	<CAL-h1aSMk=tJ9fi19vikVoo+Ff-73n4CO1vZmUL=D6Kzk23cdQ@mail.gmail.com>
	<CA+Y+447gFb6m-VVqsWOE9ApxvTha-mk6bwLTCB8ygKgwdgg3uA@mail.gmail.com>
	<29C9F273845947DD9955CD3730596E4A@cloudant.com>
	<CAKmKYaCCo3PmzZ3A8juHXuxp1_qn7NNkyf+k2KVHzkLCT5eXww@mail.gmail.com>
	<CA+Y+444XpM1Km+FyFB9eYEYHKizdVNo+_Y2iYvTwrsaV3W874w@mail.gmail.com>
	<E290D85931CD4D2D80272C3E02298C4C@cloudant.com>
	<CA+Y+446SwnB6vQRWE0Z7tZBSeXBJmzb3DgUTb-Qv6sBe4KOVmQ@mail.gmail.com>
	<CAGt9U8jSxVu2=7wqRKA+gJt-Q5C27_oWh8zWYsLdgiAxfGnLwA@mail.gmail.com>
Date: Tue, 25 Sep 2012 13:54:21 +0200
Message-ID: 
 <CAJNb-9qeG8rpq-Cf7azhxYw9B-7zomKpk=n_+Nx6UFtY8m2yoQ@mail.gmail.com>
Subject: Re: Part2: What's up dev? About couchapps.
From: Benoit Chesneau <bchesneau@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 25, 2012 at 1:30 PM, Octavian Damiean <mainerror@gmail.com> wro=
te:
>> I guess we could define a schema.
>>
>> This dir for map functions, this dir for reduce functions, this dir for
>> HTML, or whatever.
>>
>
> You mean a directory structure like the Python-based CouchApp has?


erica and couchapp (py the original) has the following schema

/
/_attachments/
/shows/*.js
/lists/*.js
/views/viewname/{map, reduce}.js
/updates/
validate_doc_update.js


/key -> a key property where the content f the ile bevome a value

/some/key ->

{ "some": { "key": ... } }

a .json is merged


There are other special file like the manifest one that allows to keep
the same structure on clone.

I think views can also be /views/viewname.map.js and /views/viewname.reduce=
.js

- beno=EEt
>
>
>> The goal is to bootstrap Futon, and to provide a simple tool to demo in =
our
>> docs.

Maybe just providing an empty db is enough? I mean a .couch that we
generate on the release.