View to handle authentication callbacks. Right now this just spits out some info.
Add Google authentication in to provide a secondary means of identity connection. Not extremly useful at this moment, but worthwhile in the future.
Adds additional fields to the identity for storing identity profile information and credentials.
Comments for general logic that needs to happen here.
unittests for a identity uid discovery function.
Grab the identity uid value from the first accounts listing.
Case for acquired the preferred uid if one has been supplied.
Just assign the user object, the orm will take care of the rest.
Test for a visitor registering with the service. Some http exception renaming snuck into this too. :P
Ensure the visitor is being redirected to their user profile page.
Adds the pyramid_tm package for transparent transaction management.
Readme rewritten to provide a description of the application and start instructions.
Fetch on initialize is good when you are certain you want to fetch, but in some cases we won't want to fetch. And so, to be consistent, don't fetch in the initialization.
The matchdict attribute is a multidict, but the attribute name is not.
Render the object to json and let the class do the work.
Render the user profile data.
Export the user collection for future proposes.
Remove these views because posting users will never happen, because users are created as an action of authenticating an identity and query will, I think, happen as part of the general listing views.
Changes the route parameter name to something more specific. This is so that views can be used within views that root at the same route. The next commit illustrates the usage of this.
Identity listing view that utilizes the get_user view to acquire the root context.