Skip to content

Custom storage support with Django #28

Open
@chandrasekharan98

Description

@chandrasekharan98

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions