Harnum, Alan" <ahar...@ocadu.ca>, Fluid Work <fluid-w...@fluidproject.org>
Subject: Re: CouchDB - managing design documents?
Hi, All.
Monday the 11th looks like the only day that works for everyone. I am waiting
to chat with Colin on his return before picking the time slot. Plea
gt; Simon
>>
>>
>> From: fluid-work <fluid-work-boun...@lists.idrc.ocad.ca> on behalf of
>> Harnum, Alan <ahar...@ocadu.ca>
>> Sent: August 28, 2017 11:19:59 AM
>> To: Tony Atkins
>> Cc: Fluid Work
>>
oun...@lists.idrc.ocad.ca> on behalf of Harnum,
Alan <ahar...@ocadu.ca>
Sent: August 28, 2017 11:19:59 AM
To: Tony Atkins
Cc: Fluid Work
Subject: Re: CouchDB - managing design documents?
Hi Tony,
Thanks for the replies – we’ve also been looking at the various Couchapp
implementations, b
ocadu.ca>
Cc: Fluid Work <fluid-w...@fluidproject.org>
Subject: Re: CouchDB - managing design documents?
Hi, Alan:
Thanks again for starting yet another interesting and important discussion.
I've had to do a lot of this in my own work, and have alternated between:
1. Storing the
Hi, Alan:
Thanks again for starting yet another interesting and important
discussion. I've had to do a lot of this in my own work, and have
alternated between:
1. Storing the design documents as raw JSON (mainly for testing). This
is similar to the approach used in the example you
Hi all,
We (Greg Moss & myself) are curious to know the opinions of others who've
worked with it (especially in the context of Infusion / Kettle) about how to
best manage design documents when using CouchDB as part of an application.
Specifically, what approaches have worked for externalizing
