Django community: RSS
This page, updated regularly, aggregates Django links from the Django community.
-
Contributing to Django Framework is easier than you think | Vinta Software
-
Getting Started with Django Channels - Real Python
-
基于nginx和uWSGI在Ubuntu上部署Django - 简书
-
longtranista/django-vue-webpack: A boilerplate of using Django as backend framework, Vue js and webpack as the frontend setup.
-
Getting Started with Django Channels - Real Python
-
Modern Django — Part 0: Introduction and Initial Setup – Medium
-
Getting Started with Django Channels - Real Python
-
Getting Started with Django Channels - Real Python
-
Getting Started With Django Channels
> In this tutorial, we will use Django Channels to create a real-time application that updates a list of users as they log in and out. -
python - Django equivalent of COUNT with GROUP BY - Stack Overflow
-
Django Book: How to Tango with Django: A Python Django Tutorial
-
James Bennett - Django in Depth - PyCon 2015 - YouTube
Covers Django's model system from database connection up through querysets and model managers. Uses django 1.8 -
Build Your First Python and Django Application | Scotch
-
GitHub - potatolondon/djangae: The best way to run Django on Google App Engine
The best way to run Django on Google App Engine -
Potato
-
Deploying Django app on AWS ECS using Docker(GUNICORN, NGINX) – Medium
-
Django Web Framework (Python) - Learn web development | MDN
-
DjangoCon US 2015 - Django Deployments Done Right by Peter Baumgartner - YouTube
-
First Django admin — First Django Admin 0.1 documentation
-
SamSamskies/django-webpack-heroku-example - Libraries.io
-
GraphQL: Slides
-
Simple django wordpress integration with Django WordPress API library
-
Table of Contents - Python Django Tutorials
The Django Book - comprehensive Python Django Tutorials, easy to understand Django documentation and more! -
Reconciling Django Templates with React Components
Abandon SPA, embrace page-as-a-component Our solution was to abandon the single page app model, and instead let Django serve each page individually, with a root React component for each page. Our base site components that don’t change between pages (e.g. navbar, footer) are provided by the Django templates, and the content specific to each page (e.g. poker interface, leaderboard) are composed within React. Abandon the SPA, why would you say such a horrible thing?! -
markfinger/python-react: Server-side rendering of React components
Server-side rendering of React components with data from your Python system Can be integrated with Django's templates