wq-django-template 1.1.0 brings Django 2 support (together with wq.db 1.1.0), as well as a restructuring of the settings to better match best practices. The old
settings.py would attempt to import
local_settings.py and ignore any errors. The new settings structure flips the order around:
settings/prod.py each import from
This approach makes it easier to use dev settings when first getting set up with wq and then switch to production settings when deploying on a public URL. The new dev settings assume SQLite/SpatialLite while the prod settings still contain a default PostgreSQL/PostGIS configuration.