> On 05.03.2015, at 20:23, Jan Lehnardt <[email protected]> wrote: > > >> On 05 Mar 2015, at 20:21, Joan Touzet <[email protected]> wrote: >> >> Is there an official couchdb build in the docker repos? If so is it >> maintained by klaemo? > > There is no build associated with the Dockerfiles, but I believe the plan is > to produce “official” CouchDB images from this. > >> Our issues with these sorts of ecosystems in the past have come from us >> perhaps not working as closely as we would like with their stakeholders for >> couchdb. If there's something similar for docker we should leverage it, or >> ensure we're closely aligned with it before we accept this. > > Yeah, this is exactly to address this. > >> -Joan >> >> P.S. In case you missed it, couchdb fell out of Debian for the Jessie >> release. :( > > Meh :/
That said: Micah et.al are getting us back on track for 2.0. And the renewed effort aims to get us on good terms with all the distros. > > >> >> ----- Original Message ----- >> From: "Robert Kowalski" <[email protected]> >> To: [email protected] >> Sent: Thursday, March 5, 2015 1:33:12 PM >> Subject: Re: [DISCUSSION] Import docker-couchdb >> >> great idea! >> >>> On Thu, Mar 5, 2015 at 6:49 PM, Jan Lehnardt <[email protected]> wrote: >>> Hi all, >>> >>> between https://github.com/apache/couchdb/pull/305 and >>> https://github.com/klaemo/docker-couchdb/issues/22 I was wondering whether >>> the docker-couchdb project would be up for donating their effort to us and >>> to take over maintenance. @klaemo is up for it and we are only waiting for >>> the one other significant contributor to give their OK. >>> >>> With that out of the way: do we want this? >>> >>> Docker can be used in two capacities for CouchDB: >>> >>> 1. spin up a dev environment with all dependencies quickly. >>> 2. spin up a production instance of CouchDB that is all self-contained. >>> >>> Our current Dockerfile serves 1., but is poorly maintained, and >>> klaemo/docker-couchdb serves 2, and @klaemo hinted at being interested in >>> taking over maintenance of 2. >>> >>> I’d be in favour of having some Docker experience in-house that can >>> maintain both use-cases and cross-share any developments. >>> >>> If I hear no objections here, I’ll move to a vote. >>> >>> Thanks! >>> Jan >>> -- >
