Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 41712 invoked from network); 9 Feb 2010 11:31:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Feb 2010 11:31:27 -0000 Received: (qmail 51125 invoked by uid 500); 9 Feb 2010 11:31:26 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 51047 invoked by uid 500); 9 Feb 2010 11:31:26 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 51037 invoked by uid 99); 9 Feb 2010 11:31:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Feb 2010 11:31:26 +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 dionne@dionne-associates.com designates 67.222.39.38 as permitted sender) Received: from [67.222.39.38] (HELO outbound-mail-158.bluehost.com) (67.222.39.38) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 09 Feb 2010 11:31:14 +0000 Received: (qmail 26477 invoked by uid 0); 9 Feb 2010 11:30:51 -0000 Received: from unknown (HELO host183.hostmonster.com) (74.220.207.183) by outboundproxy5.bluehost.com with SMTP; 9 Feb 2010 11:30:51 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=dionne-associates.com; h=Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Identified-User; b=nvr2NsYYJ/GzEjcpqjlwsAJGZhksMkVftW2sOrkVYfWbeSotu6Dy+jytj7NCB/SdM9oUgytY9KxkEcV389BFaXgx0EphnTW2ruUEY+LWOPBTqFauqAfnM5QhKNR3OlkX; Received: from adsl-99-33-198-105.dsl.wlfrct.sbcglobal.net ([99.33.198.105] helo=[192.168.1.100]) by host183.hostmonster.com with esmtpa (Exim 4.69) (envelope-from ) id 1NeoIs-0000Hr-Mn for user@couchdb.apache.org; Tue, 09 Feb 2010 04:30:51 -0700 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1077) Subject: Re: Upgrading an existing Couch's authentication From: Robert Dionne In-Reply-To: Date: Tue, 9 Feb 2010 06:30:49 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: user@couchdb.apache.org X-Mailer: Apple Mail (2.1077) X-Identified-User: {2551:host183.hostmonster.com:dionneas:dionne-associates.com} {sentby:smtp auth 99.33.198.105 authed with dionne@dionne-associates.com} X-Virus-Checked: Checked by ClamAV on apache.org Hi Aaron, Just to chime in a bit, this swinger app is way cool! I've been using = an older version of it for some time. I did do a github pull yesterday = and noticed the new authentication stuff you=20 put in. I'm not able to see my older presentations. It's no big deal = they can be readily redone, just a data point for you, my database has = been around for a while and I always run using trunk. I very happy you're keeping up with this app, it's great to give a talk = about couchdb and couchapps and be able to say "oh by the way this = presentation is a couchapp" It rocks!=20 +1 beer Best, Bob On Feb 9, 2010, at 1:20 AM, Chris Anderson wrote: > On Sun, Feb 7, 2010 at 9:18 PM, Aaron Quint wrote: >> Hey All >>=20 >> Once again, props to @jchris for getting the authentication up to >> snuff. I was able to get a simple authentication system built for my >> little couchapp Swinger: http://github.com/quirkey/swinger >> Its just so awesome that I can finally have a _fully_ functioning app >> with user accounts, without a line of server side code. (!!!) >>=20 >> So the question: >> I have couchdb on a server to host the older version of my app, and I >> wanted to push the new version with logins/etc. It _was_ running >> ~0.10, but now I've tried to upgrade it to trunk to get the auth >> goodies. I'm realizing now that theres some differences between the >> data, user data format between 0.10 and trunk. I'm wondering if = theres >> an easy way to upgrade the old data, or at least just wipe that piece >> without having to completely clear and start the data from scratch? >=20 > The user account data should be entirely in the _users db. So unless > you had one of those laying around you should be good. >=20 > Maybe I'm not fully understanding your question. It looks (on github) > like you are making progress on your app. Let us know how it goes (or > if you need more help). >=20 > Cheers, > Chris >=20 >=20 >=20 >>=20 >> --AQ >>=20 >> Aaron Quint >> http://www.quirkey.com >>=20 >=20 >=20 >=20 > --=20 > Chris Anderson > http://jchrisa.net > http://couch.io