Don't mean to be negative wrt the original python couchapp and the new one in development, but we've moved over to soca (sammy on couchapp) that comes with a nice ruby (thor-based) CLI. It also lets go of the quirky, albeit logical directory structure that couchapp enforces on you. It loses 'clone' functionality in the process but we end up with a much more straightforward project where its much easier to use coffeescript, compass as post-build pre-push hooks and extending it is also very simple. It also comes with Sammy.js instead of evently which I find much better suited for couchapps (being a Sinatra fan, to be fair).
Being a Ruby shop, it was the logical move for us but in general I find it a lot easier to comprehend and to work with. Having an Erlang configuration file suddenly pop up in my couchapp would not help the situation. Gabor On Apr 7, 2011, at 9:54 AM, bryan rasmussen wrote: > I would also prefer JSON. There are lots of tools to emit and > manipulate JSON, in my current build scenarios I am using javascript > to maintain and generate configurations, that would have to change > with erlang based configuration (or would at any rate need some new > coding) > > Thanks, > Bryan Rasmussen > > On Wed, Apr 6, 2011 at 10:13 PM, Hendrik Jan van Meerveld > <[email protected]> wrote: >> Hi Benoît, >> >> It does look readable and usable, but I have to agree with Sean that JSON >> would be much easier. >> Most users know JSON and don't know Erlang. >> >> Probably for you as a developer, changing the config file often, it will be >> easier or faster to edit in Erlang. >> For users that edit the file only once, they need time to learn some Erlang >> first. >> This way it will take normal users more time (learning time + edit time) to >> change the config file. >> >> Also if you translate your snippet from Erlang to JSON I think it will not >> be much more complex to edit. >> >> >> Kind regards, >> Hendrik Jan >> >> On 6 April 2011 18:58, Marcello Nuccio <[email protected]> wrote: >> >>> What are the advantages of using erlang for the config file? >>> Scriptability? >>> >>> thanks, >>> Marcello >>> >>> 2011/4/6 Benoit Chesneau <[email protected]>: >>>> On Wed, Apr 6, 2011 at 1:10 PM, Hendrik Jan van Meerveld >>>> <[email protected]> wrote: >>>>> Hi Benoît, >>>>> >>>>> Thanks for working on improving couchapp which is allready great. >>>>> >>>>> Would an Erlang config file be readable for a non-Erlang person like me? >>>>> What would it look like? >>>>> >>>> >>>> Here is a snippet of current work (not public yet): >>>> >>>> % log level >>>> {verbose_level, 1}. >>>> >>>> % always check app on sent >>>> {always_check, true}. >>>> >>>> % dbs urls >>>> {push_env, [ >>>> % one db push >>>> {"name", "url", [Options]}, >>>> % multiples db push >>>> {"name", [{url option}, {url, options}]} >>>> ]}. >>>> >>>> % hooks >>>> {pre_hooks, [{push, "path/to/shell'}}}. >>>> {post_hooks, [{push, "path/to/shell'}}}. >>>> >>>> >>>> I think it's enough simple to be used by anyone, isn't it? >>>> >>>> - benoît >>>> >>> >>
