使用django socialauth的混乱 [英] Confusion on using django socialauth

问题描述

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

我有点困惑我应该如何使用这个。当然，我读了底部的笔记，但我是一个Django的新手，所以我需要一个小手拿着。

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.

它的结构看起来像一个项目结构，因为它包含一个 urls.py 但我也知道那个应用程序也可以这样做。它还有一个 manage.py ，这使我相信它是一个项目（加上子目录）。

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?

README还提到抓取API密钥。所以如果我想要一个标准的界面，你点击一个谷歌/雅虎标志，它转发自己的JavaScript到你登录的身份验证页面，如果你已经没有登录，踢你回到自己的页面，我需要API钥匙？

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.

推荐答案

我们写了这个]

1. 有很多分叉，我们领先，所以你可能想使用它。
   
2. 如果你只想要openid，你不需要API密钥


3. 如果你想要twitter / FB，你肯定需要密钥。


4. urls.py和manage.py也会显示一个演示应用程序。


5. socialauth是可以拔出的django应用程序。

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.

这篇关于使用django socialauth的混乱的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！