Thanks for your reply.
After going through the tutorials for AuthKit and for repoze.who, I
ended up taking your advice and building my own simple login for basic
login and authorization.
Thanks for the response!
Steven
On Oct 15, 3:30 pm, Mike Orr [EMAIL PROTECTED] wrote:
On Wed, Oct 15
I'm a newbie trying to get a grasp on what options I have for
Authentication and Authorization. From reading the docs and the
pylonsbook.com I've found 2 options so far:
repoze.who (ported from Zope)
AuthKit (work in progress? )
Are there others?
, Steven [EMAIL PROTECTED] wrote:
I'm going through the tutorials athttp://pylonsbook.comandhave been
trying to get through the AuthKit section for a while.
I've tried both easy_install AuthKit==dev and easy_install
AuthKit=0.4.1,=0.4.9, Pylons 0.9.7, SQLAlchemy 0.5.
In both cases
group them so that ordering can be automated.
For step #5 seems like a similar strategy could be adopted as #2
Well... that was what was on my mind this morning for some reason
and I thought I'd air it out hereplease let me know what you
think.
Steven
I'm a newbie as well (working through the pylonsbook.com) in my
SimpleSite/simplesite/websetup.py I have this line at the top of the
file which defines model.
from simplesite import model
I think adding it to your websetup.py might do the trick.
Steven
On Oct 9, 11:05 am, dw [EMAIL
seeing?
Steven
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe from this group, send email to [EMAIL
.. is there a
location this is stored (the repository i found which i searched
seemed pretty old)?...any ideas?
Steven
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email
or extended so that the one-url way of doing things is
prominent.
Basically, what I'm saying is I think @validate is broken and should
be fixed, irrespective of any work-arounds that exist.
Cheers,
Steven
--~--~-~--~~~---~--~~
You received this message
On 29 Jan 2008, at 16:21, Mike Orr wrote:
On Jan 29, 2008 3:28 AM, Steven Holmes [EMAIL PROTECTED] wrote:
In my opinion, it should be *default* do the right thing, which is to
have one exposed url for a form. Or at least, the documentation
should
be altered or extended so that the one
a REST zealot
say? Seems like two different URI's for the same thing is bad.
I've hacked up my base controller class to make it work the way that
Steven wants. I suppose to me, clean URIs are better than clean
controllers. And in my case, the mess isn't in my controllers,
it's in my base
)
/account/delete -- Deletes the account (GET gives a form asking
confirmation, POST does the deletion).
This has worked very well for me so far.
Cheers,
Steven
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons
Just realised I accidentally sent this to Mike directly instead of the
list.
On 29 Jan 2008, at 23:17, Mike Orr wrote:
On Jan 29, 2008 2:55 PM, Steven Holmes [EMAIL PROTECTED] wrote:
What I was suggesting for @validate would still have two methods on
the controller, one for form
behaviour depending on
subclass.
Cheers,
Steven
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe from
13 matches
Mail list logo
