Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom storage support with Django #28

Open
chandrasekharan98 opened this issue Jun 22, 2023 · 0 comments
Open

Custom storage support with Django #28

chandrasekharan98 opened this issue Jun 22, 2023 · 0 comments

Comments

@chandrasekharan98
Copy link

chandrasekharan98 commented Jun 22, 2023

Libraries used

python = "3.9.6"
django = "^4.2.1"
djangorestframework = "^3.14.0"
social-auth-core = "^4.4.2"
social-auth-app-django = "^5.2.0"

From the django-examples, I noticed that the setting for SOCIAL_AUTH_STORAGE is commented out here. Is it because this override doesn't work as expected?

I've overriden the UserSocialAuth model similar to the example and added it a CustomDjangoStorage class and marked it with the SOCIAL_AUTH_STORAGE. But in the PostgresDB I notice tables created for the UserSocialAuth model as well. Is there any way to ensure they don't get created since we won't actually use them?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant