Settings DEBUG is True somehow

[susanodd]

The database is somehow getting locked on the production server and it's not possible to login.

OperationalError at /accounts/login/
database is locked

On attempts to login, it is showing all the settings because DEBUG is somehow set to True on the production server.

In the base.py settings, it's set to True

It looks like the server specific are not overriding this to False.

[vanlummelhuizen]

The database is somehow getting locked on the production server and it's not possible to login.

OperationalError at /accounts/login/
database is locked

I see lots of 'database is locked' in yesterday's logs. For a possible solution see #673 .

On attempts to login, it is showing all the settings because DEBUG is somehow set to True on the production server.

In the base.py settings, it's set to True

It looks like the server specific are not overriding this to False.

That is because there is no actual code doing any overriding. DEBUG = False is simply not in the code base right now. If there should be such a line, I don't know. @Woseseltops ?

[susanodd]

It seems to be in base.py

(Is that not imported if the database is locked? Should that be False?)

It's actually done "after" it imports from server_specific (in base.py)

[susanodd]

@vanlummelhuizen can you fix this bug?

The settings on the live server need to be "git stash"ed every time before a pull because there are conflicts with the master branch in the settings.
This used to not be necessary.
I don't know what the solution was in the past.