liam-m commented 8 years ago

The Auth system needs changes to accommodate the gamification/social features (#32) and the video comments/tags (#31)

@Lixquid and @ReverateNM are going to do this once they've finished the quiz changes.

liam-m commented 8 years ago

The only change we can think the comment system needs is #33. I'm happy to do this during #31.

Beornwulf commented 8 years ago

Once this is complete, it would be useful for someone who understands it to give an overview for how it works for the rest of us.

liam-m commented 8 years ago

33 is done. I don't think there's anything else that needs doing for this issue, right?

@Beornwulf: the user's details are stored in the database, which uses the DataMapper ORM. The ORM abstracts away the details of database interaction so it's wrapped up in an object.

The model is stored in user.rb.

The currently logged in user is available in the user variable (or nil).

The actual login happens in auth.rb, ignoring the developer strategy for now:

The user visits /auth/new and is redirected to /auth/google_oauth2
Google logs them in then calls our callback, which stores them in the database (unless they already exist) and stores a cookie to remember them. Aside - I think there may be a subtle bug where a user would be created when they already exist, as I mentioned in #33, but I don't think we necessarily care about this for DAMS
If the auth fails, instead an error is shown

When they log out, we remove their cookie

So when you come to implement the gamification feature you should be able to specify the relationship between badges (or whatever) and users in the model file using the associations.

liam-m / flippd

Auth system #30

33 is done. I don't think there's anything else that needs doing for this issue, right?