Closed dlanger closed 10 years ago
I'm working on creating the button links.
The social login keys and secrets are now pulled from: private_settings.SOCIAL_AUTH_TWITTER_KEY private_settings.SOCIAL_AUTH_TWITTER_SECRET private_settings.SOCIAL_AUTH_GOOGLE_OAUTH2_KEY private_settings.SOCIAL_AUTH_GOOGLE_OAUTH2_SECRET
We still need to change the dev keys to an appropriate other set of keys that we don't mind storing in source control (a different 'app' than the production keys).
Am I right in thinking this is done now?
Code wise, it's done. Production Google API and Twitter API apps need to be registered, and then their keys need to get put into the secret file for deployment.
Many thanks for this @dlanger and @cohena.
High-five @cohena, nice working with you!
Works with Twitter and Google OAuth2.
TODO
local_settings.py.dev
to replace @dlanger'sSOCIAL_AUTH_TWITTER_KEY
,SOCIAL_AUTH_TWITTER_SECRET
,SOCIAL_AUTH_GOOGLE_OAUTH2_KEY
, andSOCIAL_AUTH_GOOGLE_OAUTH2_SECRET
inlocal_settings.py.production
/login/twitter
and/login/google-oauth2