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
Add instructions for social login #11
Comments
Yes, it would be very useful to have this documented. |
The answer seems 'No'. Here is a command for creation of superuser after containers are up:
|
@ulrith you can create one like this too:
This command is going to be interactive but will work. I will add it to documentation. Thanks! |
Yes, thanks, and my command listed above is non-interactive and it works too :) |
@ulrith Also, getting social logins to work is a little tricky if you are doing it for the first time, let me know and I can help you get started. |
@maxking I'd like to accept your offer to configure social logins now :) |
@ulrith Sure! We should move to IRC or email? |
@maxking Yes thanks! I've sent an email to you |
This would also include instructions about how to disable social login via a custom |
@almereyda It should not be very difficult to just remove all the social logins. You just change the INSTALLED_APPS to remove all the social logins. There potentially could be an environment variable to disable it if enough people are interested to get rid of social logins by default, but for now, changing the INSTALLED_APPS in django's |
@maxking Hi, i tried what you suggested but it didn't not work, there is any other way to disable the external sign in from social networks in HyperKitty ? |
OK i found the solution, is as you said but, you cannot delete or comment allauth.socialaccount otherwise the migration at start up will fail. |
@Dragnell87 Yeah that would make sense because that is the only app which uses database. Although, you might be able to get rid of that if you use a fresh copy of database. Since migrations are expected to be generated by the apps, the migrate command would be expected to fail in case a table disappers without a migration.
|
This issue has not been updated for more than 1year |
https://django-allauth.readthedocs.io/en/latest/installation.html#post-installation
Django allauth requires some setup before it starts working. It needs to be setup using the django's admin console. The process isn't very difficult but needs to be documented somewhere so that people don't expect it to work out of the box.
The text was updated successfully, but these errors were encountered: