Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of pawelstawicki@gmail.com
 designates 209.85.219.213 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=gpvtEDfLh4RUINp9gC3cA7MdcF68lacaq9xLfX1bmV8ayc3G5NtJvvNkFSuBJIgn1U
         XoZS4O6U5WaQB7ZVgoRSl36q9qH0684o2raPNNTMAGVupdhwdvlq+lQDJVX0Tqoa/bAm
         512ePXoX7ouWgs7Dhq3QGyusqTSgu7RUaiA78=
MIME-Version: 1.0
In-Reply-To: <e282921e1002082220v60b707f4q305095b156ec1e6d@mail.gmail.com>
References: <a466ee761002072118u7c89bf3l48d10a8b8e3ebbc2@mail.gmail.com>
	<e282921e1002082220v60b707f4q305095b156ec1e6d@mail.gmail.com>
From: =?UTF-8?Q?Pawe=C5=82_Stawicki?= <pawelstawicki@gmail.com>
Date: Tue, 9 Feb 2010 09:55:41 +0100
Message-ID: <6adfa88d1002090055m34972753r8aed614fb1dc27bf@mail.gmail.com>
Subject: Re: Upgrading an existing Couch's authentication
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=000e0cdf9efc48a367047f2716eb

--000e0cdf9efc48a367047f2716eb
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

>From what I can see on this mailing list I assume there is something going
on around users and their rights. Is there any documentation for this new
solutions? This is something I was missing in CouchDB.

Best regards
--=20
Pawe=C5=82 Stawicki
http://pawelstawicki.blogspot.com
http://szczecin.jug.pl


On Tue, Feb 9, 2010 at 07:20, Chris Anderson <jchris@apache.org> wrote:

> On Sun, Feb 7, 2010 at 9:18 PM, Aaron Quint <aaron@quirkey.com> wrote:
> > Hey All
> >
> > 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. (!!!)
> >
> > 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?
>
> The user account data should be entirely in the _users db. So unless
> you had one of those laying around you should be good.
>
> 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).
>
> Cheers,
> Chris
>
>
>
> >
> > --AQ
> >
> > Aaron Quint
> > http://www.quirkey.com
> >
>
>
>
> --
> Chris Anderson
> http://jchrisa.net
> http://couch.io
>

--000e0cdf9efc48a367047f2716eb--