Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 38396 invoked from network); 19 Jan 2010 03:18:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Jan 2010 03:18:36 -0000 Received: (qmail 41178 invoked by uid 500); 19 Jan 2010 03:18:36 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 40967 invoked by uid 500); 19 Jan 2010 03:18:35 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 40957 invoked by uid 99); 19 Jan 2010 03:18:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jan 2010 03:18:35 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jchris@gmail.com designates 209.85.216.180 as permitted sender) Received: from [209.85.216.180] (HELO mail-px0-f180.google.com) (209.85.216.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jan 2010 03:18:24 +0000 Received: by pxi10 with SMTP id 10so1095464pxi.13 for ; Mon, 18 Jan 2010 19:18:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=N5yxer6fAz6LCD9ba+LDstso/6rZPAOFDJUEIom9rpE=; b=fOw++BRv5UK7YY5ph5eacYVJayfhyhYPoM6hLjJyrnaaACPPvBM2BEVedtIMx/p/K9 cBkLkkIqjWEEIm6/4uTaQcs5WPxfD2qtXPCtmMvnzyrj0wfVaonY9m9rEiU0/SJjwY+m aN3pha2ZVVsuZGVq3bNvM2s3LICknaj6LL7K8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=jZz+SuFtmIsVIiX8K2yQ/fDBBKD1BQkI2I6Pz2SnjUUnAmUUTgNawucdI78gayKvXh Hh63XdnmlESjJ7+0izRCJz5oGDTB7DTX6Y4xvvlFpJt5w9YrvhDTdPPXE91HWVWm0t/i 8KY7SFQFY5TwbWwCZltklfiEYi6ChZM984qAA= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.142.118.24 with SMTP id q24mr2973561wfc.237.1263871083006; Mon, 18 Jan 2010 19:18:03 -0800 (PST) In-Reply-To: <1c92f0c41001181854u4207c61bra82e73c67c1dbb3e@mail.gmail.com> References: <1c92f0c41001181854u4207c61bra82e73c67c1dbb3e@mail.gmail.com> Date: Mon, 18 Jan 2010 19:18:02 -0800 X-Google-Sender-Auth: 6b99f609f2ddf778 Message-ID: Subject: Re: Desktopcouch, per-user instances of CouchDB From: Chris Anderson To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Jan 18, 2010 at 6:54 PM, Elliot Murphy wrote: > Hi! > > In Debian there is a debate about whether to accept one of the > packaging changes that was made to CouchDB in Ubuntu: splitting the > init script into a package called couchdb, and the rest of the binary > files into a package called couchdb-bin. This allows Ubuntu to avoid > the system-wide CouchDB being started during boot of a default > desktop/netbook install, while still allowing Ubuntu One to make use > of per-user CouchDB instances. I am seeing an argument claiming that > CouchDB development "does not support" per-user couchdb instances, and > claims that the work done in Ubuntu to allow per-user instances of > CouchDB to be started on demand without ever starting a system-wide > CouchDB instance is a fork. I am baffled by the claim, but it > persists. I'm very happy that Ubuntu One is using CouchDB. I don't know enough about Debian packaging to understand that issue. It seems to me that `sudo apt-get install couchdb` should get me a CouchDB running on port 5984. It sounds like this is what you describe. On a side note, I've heard a lot of people ask how to get to the Couch that is running on their Ubuntu machine. I think making this dead simple will help dispel any notions of a fork (and encourage app development). I think per-user CouchDB's are a good idea. I'd like to see them implemented within Erlang, based on the Host header like httpd's name-based vhosts. Chris > > The Ubuntu One team has built a library called desktopcouch > https://edge.launchpad.net/desktopcouch, with some specifications > about how desktop applications should store and share records in > CouchDB http://www.freedesktop.org/wiki/Specifications/desktopcouch. > Desktopcouch exposes a D-BUS service which takes care of starting a > per-user instance of CouchDB on an ephemeral port, putting log files > in the right place, and configuring OAuth. We've contracted with some > CouchDB developers to make various enhancements to CouchDB to support > this. We've also integrated Evolution, Firefox, and Tomboy with > CouchDB (via desktopcouch), and are encouraging adoption of CouchDB by > Getting Things Gnome, Gwibber, and submitted patches to Raindrop to > use desktopcouch rather than a system-wide instance. Additionally, > applications developed using the Quickly tool automatically store > their preferences via desktopcouch, and have easy Gtk widgets which > persist data to CouchDB, and we've built a GUI tool for pairing > CouchDB systems between desktops to make it trivially easy for folks > to set up their own replication. We haven't yet written conflict or > merge widgets, but plan to soon. > > It was my impression that this use of CouchDB by Ubuntu One and > desktopcouch was accepted and supported and not at odds with the core > CouchDB development team - certainly not a fork. If anyone on the PMC > objects to the desktopcouch project and what I've described here, > could you let me know? > > -- > Elliot Murphy | https://launchpad.net/~statik/ > -- Chris Anderson http://jchrisa.net http://couch.io