couchdb-marketing mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Johs Ensby <>
Subject Re: Blog Post
Date Fri, 12 Jun 2015 03:40:41 GMT
Thanks, Johannes,

>> (for integration into npm, Grunt, Gulp…)

related to earlier discussions about lacking tools for couchapps, have you tried to set up
npm, gulp pr grunt to work as a deployment tool for couchapps?
If so, which approach would you recommend?
I very much want to keep a minimal stack of both production and development tools, and to
keep it extremely simple in developmen is important in order to build and maintain a team.
Yet, there comes a day when you realize that proper tooling needs to be put in place.
I read an article some time ago that argued for npm having most of the functionality that
people rely on grunt and gulp for.
This was especially appealing to me, as it seems that npm would be one of the tools that a
js developer should not only use, but master.
Since you mantioned npm, could you please elaborate (or event better, add to your docs) something
about your tools and use with npm?


I think you should consider giving your toolset a unique name; «bootstrap" being both generic
and dominated by the js framework could be confusing to the target group that are looking
for your tool:) 

> On 11. jun. 2015, at 20.11, Johannes Jörg Schmidt <> wrote:
> Hash: SHA256
> Let me describe what makes my tools different from the Python Couchapp
> tool and Erica.
> The bootstrap tools take the good parts of Couchapp while discarding
> the not-so good parts. They take the concept of a file based
> deployment a step further by providing a way to configure CouchDB and
> populate database security objects from files.
> You can compare Couchapp to CouchDB Push, but the latter takes a far
> more minimalistic approach while embracing some Node goodness like
> CommonJS modules and an API, as well as JSON support.
> The tools I have written are very small tools which does only one
> thing. They all offer a consistent JavaScript API and come with a CLI.
> CouchDB Bootstrap combines the tools to a high level CouchDB
> deployment tool, which can configure CouchDB, create user documents,
> replications and handle different databases.
> To recap, those are the main advantages of my tools:
> * Handle multiple documents in several databases
> * Use CommonJS modules
> * Use plain JSON files
> * Configure CouchDB
> * Write security objects
> * Provide a JavaScript API (for integration into npm, Grunt, Gulp...)
> * Following the Unix philosophy of small, sharp tools
> * Easy installation (at least for the Node folks)
> Did this answer your question, Johs?
> Johannes
> On 11.06.2015 10:54, Johs. E wrote:
>> Johannes, how would you say you tools are different from the good
>> old couchapp utility? j
>>> On 10 Jun 2015, at 17:11, Johannes Jörg Schmidt
>>> <> wrote:
>>> Hi all,
>>> I would love to cross post the Bootstrap chapter I wrote in
>>> CouchDB Best Practices on the CouchDB blog:
>>> <>
> I think it would make sense to have it in the CouchDB blog because it
>>> answers important and basic questions and helps new users to get
>>> started with CouchDB.
>>> Johannes
> Version: GnuPG v2
> adK/r9ttLh2tf+RRyIxWx520UsCkXaMOsIgW4MMb6SPziLuXOy2+9iqS92dZK/wU
> lTPZSUth/pEZzm1E2MzJ2e/jscCJSDuwYUZRwC5yeE3JXn1p7Y1HwMs/WvnaQVel
> LsUygOu5RsKQ4nNpDABUEx7DA6JNJaxIz897JYC9gCJFDGkPDrtFvq1yb1skQLaZ
> gH3oqAIM+sjwhSbrbDFwYWJmemM0sq4FLq8lGzoFuucnJP5ZvHyrhx0mWPT3pWrH
> em99hHaub3BGzJTQkUHu2SjzZpA9LJyLXtZbgDeqpdrJNYeK8xXUjWS2zG3lZ3M=
> =pxAh

View raw message