Django community: RSS
This page, updated regularly, aggregates Django links from the Django community.
-
A breakdown of how NGINX is configured with Django
-
Django 3.1 async
-
lincolnloop/goodconf: Transparently load variables from environment or JSON/YAML file.
-
Django 2.0 url() to path() cheatsheet - Considerate Code
Great explanation of new style urls - and how to convert from the old Django 2.0 introduced a new way to define URLs, which greatly simplifies how parameters are captured. In earlier versions of Django, you had to use the url() method and pass a regular expressions with named capturing groups to capture URL parameters. url(r'^posts/(?P[0-9]+)/$', post_detail_view) In Django 2.0, you use the path() method with path converters to capture URL parameters. path('posts//', post_detail_view) path() always matches the complete path, so path('account/login/') is equivalent to url('^account/login/$'). -
A breakdown of how NGINX is configured with Django
-
django-allauth · PyPI
-
How to Use Email as Username for Django Authentication :: Tech Blog — Serhat Teker
-
Surviving Django, if you care about databases | Hacker News
-
Flask with Django ORM
Flask with Django ORM in a GitHub Gist -
Andrew Godwin on Twitter: "Reading some of the positive comments about Django migrations this evening is giving me warmth. This is why I write open source software. (though I think you should still have at least a few DBAs, they're very handy!) https://t.
-
Surviving Django (if you care about databases) — Daniele Varrazzo
-
Surviving Django, if you care about databases | Hacker News
-
Surviving Django (if you care about databases) — Daniele Varrazzo
-
Surviving Django (if you care about databases) – Daniele Varrazzo | Hacker News
-
XSS Exploitation in Django Applications
In this article, I’m going to cover various exploits that can work against the Django templating engine in a modern web application. I’ll show how and why they work, as exploits, the risks of leaving them unfixed. Then, I’ll show you how to find them using a fuzzer I’ve been developing. (via Pocket at August 05, 2020 at 11:41AM ) -
Django Lifecycle Hooks
-
django-queryable-properties — django-queryable-properties 1.3.1 documentation
-
django-model-utils — django-model-utils 3.2.0 documentation
-
Home - Jazzmin
-
Home | Django Template Tags and Filters
-
Customizing the Django admin
-
Lets Build a music streaming app with Django ,vuejs , Django rest framework and jwt - Part 2 | GSPACE
-
How to Make Always-Installed Django Database Instrumentation - Adam Johnson
Since version 2.0, Django has provided a hook for installing database instrumentation wrapper functions. These functions are like middleware for database queries, allowing you to inspect and rewrite SQL before it is sent to the database. There are many use cases, for example: Blocking database queries in certain blocks of code, as in the feature documentation. Tracking all queries, as in Scout APM’s python agent. Rewriting queries to add extra SQL features, as used in Django-MySQL’s query hints extensions. For this post, let’s use an example wrapper function that logs a warning for slow queries. We can implement it like this: -
torchbox/django-pattern-library: Pattern libraries for Django projects
A module for Django that helps you to build pattern libraries and follow the Atomic design methodology. Objective At the moment, the main focus is to allow developers and designers use exactly the same Django templates in a design pattern library and in production code. There are a lot of alternative solutions for building pattern libraries already. Have a look at Pattern Lab and Astrum, for example. But at Torchbox we mainly use Python and Django and we find it hard to maintain layout on big projects in several places: in a project's pattern library and in actual production code. This is our attempt to solve this issue and reduce the amount of copy-pasted code. Documentation -
torchbox/storybook-django: Develop Django UI components in isolation, with Storybook
Storybook for Django is an experimental UI development environment for your Django UI components. Work on components in isolation from your site or app. Test them with mock data. Document as you go. Have a look at our online demo.
