Confusion on using django socialauth

Question

http://github.com/uswaretech/Django-Socialauth/tree/master/socialauth/

I'm a bit confused on how I should use this. Of course, I read the notes at the bottom but I'm a Django novice so I'll need a little hand holding.

The structure of this looks like a project structure since it contains a urls.py but I'm also aware that applications can also have that. It also has a manage.py which leads me to believe it's a project ( plus the subdirectories ).

So should I just be integrating portions of this into my existing project? This isn't an application, right?

The README also mentions grabbing API Keys. So if I want a standard interface where you click on a google/yahoo logo and it forwards itself via Javascript to the authentication page where you login if you already aren't logged in, kicks you back to your own page, would I need API keys?

Any other special tips are appreciated.

Answer 1

[We wrote this]

1. There are quite a few forks, which are ahead of us so you might want to use that.
2. If you just want openid, you dont need API Keys
3. If you want twitter/FB you definately need keys.
4. urls.py and manage.py are too show a demo app.
5. socialauth is the django app, which you can pull out.

Answer 2

I would use the fork from agiliq (same guys).

If you look at the commits in agiliq and uswaretech, you will see that the agiliq fork has more recent commits.

• https://github.com/agiliq/Django-Socialauth/commits/master
• https://github.com/uswaretech/Django-Socialauth/commits/master

And you could also use django-social-auth, which might seem to be another fork, but it's a completely different implementation.