Hi Ken,

Thanks for your reply. I have tried many examples/suggestions for the
last two weeks. I really spent the time to create the app and followed
the examples steps by steps. Most of the instructions works for the
simple cases where the data stored in the configuration or in
filesystem. But what I need is to have the users data stored in a
database and using SQLAlchemy driver. That didn't work for me so far.
That makes me very nervous to suggest and really focus on starting a
brand new production app based on pylons.  Have anyone better luck
with this setup please help, I am still searching...

Thanks,
minh


On Feb 15, 1:26 pm, "Garland, Ken R" <[EMAIL PROTECTED]> wrote:
> well it's been a while since i setup my authkit+homegrown solution and
> i never really documented it properly. but i must say that it was a
> great way to really learn the ins and outs of pylons. my advise is to
> just give it a shot and follow some howto's, see what you can come up
> with.
>
> but it has been a while since i've been up to date on pylons
> developments and documentations so there may be one out there that is
> 100%.
>
>  - Ken
>
> On Thu, Feb 14, 2008 at 9:12 PM, minhl <[EMAIL PROTECTED]> wrote:
>
> >  Dear all,
>
> >  I have looking around for a reliable way of doing authorization and
> >  authentication with Pylons application. So far, all I found are either
> >  the homegrown way or the AuthKit ways. I like the AuthKit solution but
> >  none of the examples that I came across were working. I need to have
> >  the users data stored in the database. Would anyone have any
> >  suggestion?
>
> >  Regards,

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to