Django

“The obvious thing that makes it unique (from, say, Prettier) is that it supports HTML templates; We run it on Django templates.”

“We switched our very large Django monolith codebase over to ty”

“I've been using django & duckdb together, which keeps me from using the ORM.”

“At my day job we use Django with HTMX and Alpine, but we also generate the custom CSS from Pico”

“One running on their own hardware, Django + Celery. The other one running on AWS EC2, Django alone.”

“which used to consume APIs written with Falcon, Django and FastAPI.”

“In an app I'm working on, once we switched to PGVector in Django the need for a lot of things went away.”

“We had a Django application backed by PostgreSQL... we've had a few hiccups with autogenerated migration scripts”

“the django project we use is installed locally and something somewhere made it so I couldn't run migrations”

“The Django equivilent is having different settings for prod vs dev, and for good reason”

“We use that, a base model and some mixins, but we use Meta.abstract=True”

“This rightly could be Django's fault, but Form, Model, Serializer validations are all separated and cannot be unified.”

“our main service which is a rather large REST API... it's a Django app”

“We do something similar, multiple django sites and static sites on a single digital ocean droplet.”

“I came to it from a Python Django thing.”

“I teach it to my students (Python, flask, Django..).”

“as someone who has been working with Django for years, my standards are pretty high”

“collectstatic when DEBUG is set to false... it's 100% the same for Django.”

“We've got a Django site that we run in production for different partners.”

“The site ran using only 7 servers, including encoding, streaming, database and the django app itself”

“building real-world web products in pre-SPA simple Django + jQuery (2012-2015)”

“As a Django shop, we've always hoped PyPy would one day be suitable for our production deployments”

“fullstack Python + Django -> frontend role with backbone/knockout/angular”

“I've been using this for most projects with a Django backend.”

“I've been a Django dev for years but now that all projects have pretty much moved to client side js + drf backend anyway”

“I've been using turbolinks and stimulus with Django for a good year and a half.”

“We've been simply throwing huge Django projects into Zappa and seeing huge benefits.”

“This was in a django web app, nearly a decade ago. First team I was on professionally”

“I haven't defined profiles such as dev or production for a really long time, with Django projects in particular.”

“For a long time, we ran our Django test suite against an in-memory SQLite DB.”

“the elixir backend replaced a flawed stateless django program”

“I've been using Django since 0.96 and I didn't know half of the items in this article.”

“The DB is created or updated with Djangos migrate command which runs when the Docker container starts.”

“a half-baked python/django effort that is currently in prod”

“I've tried to use Zappa for a non-trivial personal project to run a Django app”

“For this project (which is still in production), we ended up falling back to a standard Gunicorn web server setup”

“Most of the biggest improvements to Django came after Adrian and I stepped down and we moved to a more democratic leadership structure.”

“I built a very rudimentary digital / electronic signature tracking app in Django several years ago”

“And except for that, I visit the django docs and stackoverflow every day, of course :)”

“our backend is in Python Django and Pyrebase comes with its own set of issues”

“when I kept all my work in django templates, erb, blade, etc. and just script JS by hand”

“If any major/breaking version of react/django/drf comes out, we pause and update the tech stack.”

“In Django 1.10, we switched the CSRF token generation to use a consistent base value”

“Web infrastructure developer (we use oracle dbs, django, various RPC services etc)”

“getting it setup isn't such a breeze”

“We build a web UI in Django that raises Celery tasks that run long number crunching jobs.”

“building dashboards in Django to display data collected.”

“(Django, Flask, Tornado on uWSGI). This simplified deployment and administration quite a bit.”

“I currently have a Django-based intranet site (Windows Server 2012 w/ MSSQL DB) and will also have a web-app with the same set-up”

“We've run through PHP, Rails, Node, Python (Django) and lately Go.”

“We've run through PHP, Rails, Node, Python (Django) and lately Go.”

“We've ditched Django templates entirely. We use it as our API platform only”

“We've moved to Docker Compose for local Python (Django) development.”

“we used uWSGI to front our Django application”

“we replaced most of our cron jobs with celery and django celery fulldbresult”

“I have been working on a Django application with two periodic background tasks”

“Django is great, except for the thing we do / the expertise I / we have.”

“Learning ruby, rails, and django”

“The missing CMS built with python/django. We use in our agency for a lot of projects, including high profile brands.”

“experiencing Django and Node was an eye opener.”

“we switched from ASP.NET MVC to Django, got a Django guy in our team.”

“I use an Acer C720P as a backup dev machine for a Django project.”

“it's based on Django under uWSGI, and all of the services run within Docker containers.”

“I just used it to provision a new server (from zero to full Django stack) in 30 seconds.”

“I have quite a few projects based on django, and these are still 2.7.”

“We run many more than 12 processes per server. That's how you can get around that.”

“We're a django shop, and pt-online-schema-change is an amazing tool.”

“The technologies we use are pretty standard web dev stuff (HTML/CSS/JS and Python/Django).”

“I use South on a fairly substantial django project (35 models, 85+ migrations).”

“Also mostly confident we're still the "largest Django app" in terms of traffic.”

“We use their cheaper dedicated machines for our application servers (running Django, memcached and celery workers)”

“underlying data store are non django models, security is very granular”

“I too wrote a REST app for Django”

“I'm currently building using Django/jQuery/Bootstrap. My last project was GAE.”

“before we switched to Django for all our development so I haven't kept up”

“we use Django / python / Asterisk as our primary tools, along with OpenSIPs for routing SIP traffic.”

“I have some apps deployed with nginx > uwsgi > django”

“I tested Django, Rails, Cake, Java EE and buncha other stuff.”

“It's what we use at Mozilla as the basis for most of our Django-based stuff”

“I don't want to start a Rails or Django project (yes, I use both) just for the sake of having transparent precompilation”

“Having briefly toyed with it in the past”

“It had MySQL with a prod snapshot, RabbitMQ, a Django web app and a bunch of twisted services.”

“I'm using a Django template tag, {% static "css/example.css" %}”

“I've build a blog in Django :D”

“I wish we could use Django's autoescape filter but App Engine's SDK ships with just 0.96 by default.”

“Ours was a Python/Django app and just took a few lines of configuration to get up and running.”

“I wrote my own deployment scripts to deploy django-based projects.”

“So for templating, database interaction and so on I'll keep using Django.”

“Django for templates, JSON, BeautifulSoup, Markdown”

“Using Django with my prototyping framework is by no means an endorsement”

“one of our requirements is that new features be documented”

“We keep a local settings file for each environment... which in turn is imported into settings.py.”

“We use mod_xsendfile instead (with another Django helper app, which I'm hoping to get onto Bitbucket in the next week or two)”

“Turns out that one of my Django models is breaking the Django admin interface”