couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bryan rasmussen <rasmussen.br...@gmail.com>
Subject Re: The new couchapp. [cr]
Date Thu, 07 Apr 2011 07:54:30 GMT
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
<haaiee@gmail.com> 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 <marcello.nuccio@gmail.com> wrote:
>
>> What are the advantages of using erlang for the config file?
>> Scriptability?
>>
>> thanks,
>>  Marcello
>>
>> 2011/4/6 Benoit Chesneau <bchesneau@gmail.com>:
>> > On Wed, Apr 6, 2011 at 1:10 PM, Hendrik Jan van Meerveld
>> > <haaiee@gmail.com> 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
>> >
>>
>

Mime
View raw message