Safe Django migrations without server errors
How to run schema-changing Django migrations safely, avoiding schema/code mismatches and server errors during rolling deploys. » Kevin Renskers | loopwerk.io
How to run schema-changing Django migrations safely, avoiding schema/code mismatches and server errors during rolling deploys. » Kevin Renskers | loopwerk.io
Using background tasks to reliability execute signal receivers » Haki Benita | hakibenita.com
Did you know that you can run unit tests for your Django app, in GitHub Actions, using PostgreSQL? » Kevin Renskers | loopwerk.io
Comparing the Django ORM support across official database backends, so you don’t have to learn it the hard way. » Paolo Melchiorre | paulox.net
Django integration for PostgreSQL Anonymizer extension » Django Packages | djangopackages.org
The original DjangoBook is now online again at DjangoBook.com » Will Vincent | wsvincent.com
PyPI, pedalboard, Django URL Patterns, and More » PyCoder’s Weekly | pycoders.com
Full Django in a single file - views, models, API ,with async support. Automatically convert it to a full project. » Django Packages | djangopackages.org
Learn tips and tricks about web development with Django daily » Aidas Bendoraitis | djangotricks.com
Adam Hill posted a question on Mastodon: he wants a model field that uses choices that doesn’t generate a database migration when the choices change. This post presents my answer. First, we’ll recap Django’s default behaviour with choice fields, a solution with callable choices… » adamj.eu | adamj.eu