-
Notifications
You must be signed in to change notification settings - Fork 14
Enabling social-auth breaks manage.py prep #106
Comments
Oh, I see psycopg2. And does it work with the default DATABASES settings (which use sqlite)? |
Yes, sqlite works. And I do not think that caused any bad side effects, but probably I'm wrong. I'm doing so because I use django-environ to configure my settings (I plan to use Heroku and/or Docker to deploy). |
Hi @telenieko , |
Also if you want to have DATABASES untouched, just define it after the line SITE = Site(...) in your settings.py file. |
We didn't yet use neither django-environ nor Heroku nor Docker so far. And I guess that we should do so. It's just a lack of time. Maybe one day you should give us some lessons... |
Up to now what I've found is that SQLite works but psycopg2 does not. On SQLite:
On PostgreSQL:
Crearly something's off there. Will keep investigatin. |
Indeed, Lino's initdb command is not tested with PostgreSQL: |
From a quick glance to that file:
I'm willing to bet the problem is there. That running migrate first prevents the "--run-syncdb" to have any effect later. Will do some testing later |
Hi there,
I'm on python 3.6.8, lino==19.2.2, lino-xl==19.2.0;
When I follow the social authentication page on the book
mange.py prep
won't work anymore.In my Site class I do:
social_auth_backends = [ 'social_core.backends.google.GoogleOAuth2', ]
, and then set the appropiate settings for the backend and when runningprep
this comes:The furthest I came is that initdb does first the migrations and after migrations it does the non-migration capable applications. What happens (I think) is that modlib.users is not migration capable while social_django is.
So tables for social_django are created before modlib.users tables even exist, hence the exception.
The text was updated successfully, but these errors were encountered: