You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Django 4.2 introduced a unified STORAGES setting which unifies static & media setup and simplifies adding a custom storage that might be required by an application (e.g. private media).
Hello @browniebroke ,
Currently I am working on it and it passed all the Templates Test Suit. But Generate project tests fails with django.db.utils.OperationalError: connection is bad: No such file or directory error message. (using test_bare.sh)
Do we need local database running? where am I wrong?
Yes, this test script needs a database. You can see how it's used in our CI workflow, there is service which is started.
It's great that you're trying to test locally, but don't spend too much time on the non-docker tests, the setup can be quite complicated, they'll run on GitHub when you open a pull request.
Description
Django 4.2 introduced a unified
STORAGES
setting which unifies static & media setup and simplifies adding a custom storage that might be required by an application (e.g. private media).Rationale
The
DEFAULT_FILE_STORAGE
andSTATICFILES_STORAGE
settings are now both deprecated and we should migrate to the new setting before Django 5.1The text was updated successfully, but these errors were encountered: