Login

r/django

Note taking and todo app
▲ 2 r/django+3 crossposts

Note taking and todo app

Hey everyone, following up on my original post (https://notatask.com) about NotaTask (simple task + note management app). Thanks for all the feedback last time — here's what changed:

UI got a full rewrite. The old UI was Bootstrap and, frankly, kind of shitty. It's now completely rebuilt on Tailwind CSS with a proper dark theme. Several of you said the old UI felt complicated/cluttered — this was the direct fix for that.

Android app is live. There was no mobile app before — it's completely new, built with Flutter, and talks to the same backend. You can grab it here: https://play.google.com/store/apps/details?id=com.notatask.app&hl=en

iOS — PWA for now. No native iOS app yet (no paid Apple dev account), but the web app is now fully responsive, so it works well as a PWA / installed home-screen app on iPhone in the meantime.

Web is responsive too. If you're not on Android, the site itself now works properly on mobile browsers as well.

Behind the scenes: added automated daily database backups, so things are more production-safe than before.

Still just me building this on the side around a full-time job, but slowly chipping away at the feedback from last time. Let me know what you think of the new UI, and if the Android app breaks on you, happy to fix it.

https://notatask.com

u/heisenbug403 — 2 days ago
▲ 7 r/django

django-fastmig

Released an experimental package making migrate much faster in large projects. Especially useful if you do pytest -create-db frequently, or run reverse migration testing in CI. Django's own test suite passes with fastmig. Also tested on a 8 year old project with multiple revisions and migration squashes over the years.

Made it to speed up my own testing being bottlenecked by -create-db.
There's a link in readme related to forum posts which discusses slow migrations.

https://github.com/viktor2097/django-fastmig

u/Then_Listen413 — 3 days ago
▲ 12 r/django+2 crossposts

Software Engineer available for freelance / contract projects

Hi everyone,

I’m a Software Engineer, currently looking for freelance, contract-based, or project-based software development opportunities or Permanent opportunities.

I have experience building software for clients and working on full-stack applications. My main technologies include:
• Next.js / React / TypeScript
• Node.js / NestJS / Express.js
• .NET / ASP.NET Core / C#
• Angular
• PostgreSQL / MySQL / SQL Server / MongoDB
• REST APIs and backend development
• Authentication, payments, booking systems and dashboards
• Git, GitHub, Azure DevOps and modern deployment workflows

I’ve worked on real world client projects as well as several full stack applications, including booking platforms, management systems and SaaS applications.
I’m flexible with working hours and can work with teams across different schedules. I’m open to long-term, short-term projects, ongoing freelance work, or contract engagements.

Portfolio: www.abirampathmanathan.com

If you or your company has a project where you need an extra developer, feel free to DM me here on Reddit. I’m happy to share more about my experience, GitHub and previous work.

Thanks!

reddit.com
u/abiram19 — 3 days ago
▲ 50 r/django

Why I signed up to donate $50 a month, and you should consider it too

Hi Djangonauts,

I've had a thought in a long time, which is I should donate to Django, I just never got around to do it. Finally I made that thought a reality.

I've been using Django for probably 4-5 years now, and it's become the main core in my projects, so I am really dependent on the project, and if it stopped being supported it would be a disaster. This is the most important backbone, and we pay for all other services, but not this one core project.

Djangos support goal is $500,000, and they are behind this years goal by nearly $100,000. I wish I could donate more at the time, but the day my company is earning more revenue I will upgrade my pledge to a higher number (now the thought is realized, it's much easier to increase).

Django has shown us over the years that they can be trusted with creating software, and they are really good at it. So if you think so as well, please visit the Donate Page and see if you get the same urge I did.

djangoproject.com
u/Frodothehobb1t — 4 days ago
▲ 9 r/django

Django JSONStore: typed model fields backed by nested JSON

I have just released a new version of Django JSONStore.

Many Django projects keep one-off or fast-changing business data in a JSONField. This is flexible, but requires additional code when you need a ModelForm or want to edit the data in Django admin. Moreover JSON internal structure became exposed all over codebase.

JSONStore maps any path in the document to a typed virtual model field. These fields work as a regular data assessors, in ModelForms and Django admin like normal model fields. They also support filters, ordering, values() and values_list().

from django.db import models
import jsonstore


class Employee(models.Model):
    data = models.JSONField(default=dict)

    full_name = jsonstore.CharField(
        max_length=250,
        json_field_name="data",
        json_key=("profile", "full_name"),
    )
    hire_date = jsonstore.DateField(
        null=True,
        json_field_name="data",
        json_key=("profile", "hire_date"),
    )


employee = Employee(full_name="Ann Lee")
employee.data
# {"profile": {"full_name": "Ann Lee"}}

Employee.objects.filter(full_name="Ann Lee").order_by("hire_date")

This keeps rest of code, free from knowledge of json internals, leaves your option to migrate to standalone Django model column later.

You can also expose a whole nested document as a typed jsonstore.EmbeddedModel with EmbeddedField, or a list of documents with EmbeddedListField. You even can use emulation of document-backed ForeignKey, OneToOneField and ManyToManyField fields.

Use JSONStore for business data that changes often and doesn't make sense to get aggregated data.

GitHub: https://github.com/viewflow/jsonstore
Website and examples: https://django-jsonstore.viewflow.io/

u/kmmbvnr — 4 days ago
▲ 4 r/django+1 crossposts

How much would you charge for a custom Django car-rental website like this?

I’m building a website for a car-rental company that has multiple branches/locations across different countries, and I’m trying to estimate what a project like this would normally cost.

The website would include:

  • Modern, responsive frontend
  • Django/Python backend
  • Database integration
  • Admin dashboard for managing the website
  • Car listings with dynamic information
  • Individual car details pages
  • Car rental/booking functionality
  • Different branches/locations
  • Services and company information pages
  • Blog
  • Contact/inquiry functionality
  • Responsive design for desktop, tablet, and mobile
  • Professional UI/UX
  • Deployment and setup

The goal is to have it function as a proper car-rental website/platform, rather than just being a static company website.

What would you consider a reasonable price range for a project with this scope, in USD?

reddit.com
u/Familiar_Hotel2912 — 5 days ago
▲ 10 r/django

Do you actually use the DTL for the frontend in production or setup REST for ReactJS/Other conventional frontend frameworks?

I come from Nest so I might be a bit biased but I feel like frontend tools like React and Angular are disproportionately more powerful and come with a lot of support and plugins (npm packages).

Do you actually use the DTL in production or just as a testing tool?

reddit.com
u/daniel_zerotwo — 4 days ago
▲ 1 r/django

Where do you write down the reasoning behind old migrations and managers?

I have been on the same Django project since 2018, and what slows me down now is that most of the non-obvious lines have a reason that lives outside the repo. Coming back to an app I have not touched in months means reconstructing that reason before I can change anything.

Data migrations are the sharpest version of this. A RunPython backfill encodes a rule about how existing rows should be interpreted, it runs once, and then it sits there as the only written record of a decision nobody remembers making. Custom managers are close behind. Someone narrowed the default manager years ago and everything that goes through objects has inherited that filter ever since without announcing itself. git blame gets me to a commit called "fix dashboard timeout" and stops.

So I have started writing two or three sentences of why into a docstring at the top of the migration instead of the PR description, on the theory that migration files are the last thing anyone deletes, squashes aside. I write them while the migration is still in front of me, in the same session as whatever assistant I have open, currently verdent, which carries memory across sessions. A decisions doc went stale inside a month. The docstring has held up better, mostly because it turns up in the diff.

Where do other people put this? A docstring on the model, a per-app notes file, the commit body, or do you just redo the archaeology every time?

reddit.com
u/DigitalDrifter-01 — 4 days ago
▲ 3 r/django

django-captcha-kit — A simple CAPTCHA library for Django

Hi everyone,

I’ve developed django-captcha-kit, a small Django library for adding CAPTCHA protection to forms, with the ability to switch between providers through configuration.

Supported providers:

  • Cloudflare Turnstile
  • Google reCAPTCHA v2 (checkbox)
  • hCaptcha
  • Image CAPTCHA — locally generated distorted characters, with no third-party service
  • Math CAPTCHA — fully local, using a signed token and no server-side state
  • none — disables CAPTCHA, useful for testing and development

The goal is to keep the API simple while supporting both external CAPTCHA providers and fully local CAPTCHA implementations.

There are no dependencies other than Django. Verification relies only on the Python standard library. The Image CAPTCHA provider is the only one that requires Pillow, and only if you install it explicitly:

pip install django-captcha-kit[image]

GitHub: https://github.com/Macktireh/django-captcha-kit

PyPI: https://pypi.org/project/django-captcha-kit/

I’d be interested in your feedback!

Best regards, and have a great weekend.

u/Remarkable-Bag4365 — 6 days ago
▲ 0 r/django

How I structure a Django project for production from day one

One of the things I have changed over the years is how much structure I put into a Django project before building the first real feature.

Django’s default project structure is a good starting point, and for prototypes or smaller applications I am quite happy to keep things simple.

The problems tend to appear later.

A single settings.py grows environment-specific conditionals. The default user model becomes difficult to replace. Business logic starts appearing in views. Shared code gradually accumulates in utils.py. Deployment configuration lives partly in the repository and partly in someone’s memory.

None of these are particularly difficult problems at the beginning of a project.

They become much more expensive once the application has production data, integrations and multiple developers working on it.

I now make a small number of structural decisions early:

- Split settings by environment
- Create a custom user model before the first migration
- Organise Django apps around business responsibilities
- Keep the core app deliberately small
- Give business logic a clear home outside the HTTP layer
- Treat APIs as another interface to the same application logic
- Keep infrastructure such as storage and email configurable
- Make testing and deployment part of the project from the beginning

The important distinction for me is that this does not mean building everything on day one.

I do not need Redis, Celery, Sentry or cloud storage running locally before I have written a feature. I just want the project to have an obvious place for those concerns when they arrive.

That is the balance I try to strike between keeping Django simple and avoiding completely predictable restructuring later.

I have written up the full project structure I use, including settings, apps, services, APIs, background tasks, infrastructure, testing and deployment:

https://www.digitaledgeconsulting.co.uk/blog/how-i-structure-a-django-project-for-production

As with my previous post about service layers and thin views, this is not intended as the correct way to structure every Django project.

It is simply the structure I have arrived at after building and maintaining larger Django applications in production.

I would be interested to hear which decisions other people make at the start of a production Django project, and which ones you deliberately leave until later.

reddit.com
u/PrizeThing6131 — 6 days ago
▲ 3 r/django

Looking for honest feedback on my Django/DRF e-commerce project

​

Hi everyone,

I'm a final-year CS student preparing for my first Python/Django backend role. I recently built this e-commerce project and would really appreciate an honest review from experienced Django/backend developers.

**GitHub Repository:**

https://github.com/abhishekc8205/django-ecommerce-platform

### Tech stack

* Python

* Django

* Django REST Framework

* SQLite

* JWT authentication

* Stripe

* Pillow

### What the project has

* User registration/login/logout

* Buyer and seller functionality

* Seller product management

* Product search, category filtering, sorting and pagination

* Product variants (size/color)

* Product image galleries

* Customer reviews

* Shopping cart

* Checkout flow

* Stripe checkout with local testing fallback

* Seller sales dashboard

* REST APIs for products and categories

* JWT access/refresh token APIs

* Seller-only permissions for creating/updating/deleting products

I'm targeting **Python/Django backend fresher roles**, so I'd especially like feedback on:

  1. Is this strong enough to be my **main resume project**?

  2. How would you rate the Django/DRF implementation?

  3. Does the project look like more than basic CRUD?

  4. Are there any obvious bad practices or security issues I should fix?

  5. Is the authentication/authorization approach reasonable?

  6. What parts of the code would you improve?

  7. What features would actually make this project stronger for backend interviews?

  8. If you were interviewing me based on this project, what questions would you ask?

  9. Would you consider this a good project for a **Django backend fresher**?

I'm looking for **honest criticism rather than compliments**. I want to improve the project before using it in my job applications.

Thanks in advance for taking the time to review it!

u/abhi825c — 6 days ago
▲ 10 r/django

Have you ever needed a composable, reusable WebSocket framework - like DRF, but for Channels?

Hi all, I maintain a utility package that extends Django Channels (WebSocket/ASGI). I'm thinking about building a small framework in the same spirit as DRF and its ecosystem, but aimed at Channels/WebSockets - things like audio streaming, notifications, bidirectional chat, chat rooms, and so on.

Before I start, I wanted to ask the community: have you ever needed something like this? For example, you had to implement a WebSocket feature, struggled with it, and went looking for a tutorial or library that already solved the problem and came up empty.

If these are real pain points, I think there's room for a reusable library. Looking forward to hearing your thoughts.

reddit.com
u/huygl99 — 8 days ago
▲ 5 r/django

Need Tips and Recommendations on migrating a project from ASP.NET MVC to DRF.

On the company i work for, we mostly use DRF, but there is this one project, written on .net mvc, that no one dares to touch anymore, the plan is to migrate the project, it is sort of small. The site Its a webapp, that serves a tool for business to hire new people, and helps managing the process of hiring someone. We used to use it only for ourselves but we are planning to sell the solution to the public.

The site on .Net is gonna continue to be up (which no one uses anymore), and we are gonna be migrating to DFR on another completely different server, we are gonna be testing until its done then we are gonna take down the .Net server.

Somehow I got stuck as a tech leader even when i'm nothing of the sort, and I have to lead my team on migrating the app. Which is something i have never done before tbh. So that's why i come to you all, to give me some tips on how to approach this move, what would you recommend to start with?? I don' t want to make this more complicated than it should. Like should i start with models or matching controllers to views ... im so open to hear your opinions and tips.

reddit.com
u/roseekilljoy — 7 days ago
▲ 34 r/django

Django Control Room 1.7.1: Broad theme compatibility

This release significantly expands theme compatibility for DCR to many more alternative admin packages used in the Django ecosystem.

  • Automatic theme switching: There is no longer any need to explicitly load any adapter css; If you are using a different admin (e.g. unfold, or jazzmin) The appropriate theme adapter will be loaded automatically if it exists and for all panels. You can always turn this feature off and control exactly what css or adapters are loaded.
  • New theme adapter for django-admin-interface. This is a popular alternative admin package that lets you switch themes at run time by virtue of theme data being persisted in the database. It also provides a mechanism for you to build your own custom themes and comes with several examples. DCR now supports themes created by this package.
  • New theme adapter for Dracula: The popular color theme for code editors and other places has a django admin theme dedicated to it. This is a very light color scheme for the admin that I think more people should try. DCR now supports it via a direct theme adapter.
  • Generic theme adapters: While larger footprint packages (unfold, jazzmin, etc) have dedicated theme adapters built for them, this is not a scalable strategy given how many possible admin packages may exist. General theme adapters have now been built that are loaded for many different packages. This allows DCR to work for many more packages than the themes and packages given first party support. You can see a full compatibility matrix here: https://django-control-room.github.io/dj-control-room/themes/

This release marks the completion of a wave of changes aimed at allowing DCR to function in most admin environments. It's also the end of a series of migrations for existing panels toward using a common core library that normalizes how panels operate (giving them all theme abilities for example)

Next:

  • A panel dedicated to errors
  • making it easier to build panels
  • simplifying messaging/docs
  • No more theme stuff, but will gladly accept PRs for themes

Repo: https://github.com/django-control-room/dj-control-room

Roadmap: https://github.com/orgs/django-control-room/projects/1/views/3?filterQuery=-status%3ATodo

Edit:

quick way to update all your panels:

pip install --upgrade "dj-control-room[all]"

u/yassi_dev — 9 days ago
▲ 0 r/django+1 crossposts

Build API in one line code with FlashAPI

What if creating a REST API in Python no longer required writing the same boilerplate over and over again?

I created FlashAPI to answer a very simple problem:

When we develop an application, we often spend time rewriting the same things:

→ RAW

→ pagination

→ search and filters

→ sort

→ permissions

→ exports

→ soft delete

→ audit

→ repetitive endpoints...

The problem is not to know how to develop them.

The problem is having to redevelop them with each project.

With FlashAPI, you define your Python models and you automatically get a complete REST API around them.

⚡ Compatible with FastAPI, Flask and Django

🐍 Pydantic, SQLAlchemy, dataclasses

🔓 Open source under Apache 2.0

🚫 No proprietary runtime, no vendor lock-in

And above all, FlashAPI does not seek to replace your code.

You keep your business logic, your personalized routes and the ability to disable or customize what you don't need.

The objective is simple:

Less boilerplate → more time to build what makes your application unique.

👉 GitHub: https://github.com/HackermanMe/flashapi

I am now looking for Python developers to test and contribute.

#Python #FastAPI #Django #Flask #OpenSource #Backend #RESTAPI #SoftwareEngineering

u/rakakayiouu — 8 days ago
▲ 1 r/django

Dsa or Django?

I am fairly new into programming. So I am familiar with the basics of python. Have made some terminal based projects as well. Started dsa concepts yesterday but it is boring me out. I do plan on learning both but is it a good idea to get some real experience with django and web projects first? (I have knowledge of html, css and little bit js)

Also, I am in my first year of graduation so time is not a concern!

reddit.com
u/shubham_555 — 8 days ago
▲ 9 r/django+1 crossposts

django backend vs frontend

Hey everyone, i recently stared learning django and i have realized that the frontend matters more than i thought. My goal is to become a backend developer, but the more web apps i make the more i realize that i need to learn the frontend(HTML + CSS + JS) as well, because it is the thing that is being shown and it can work flawlessly but if it looks like shit no body is gonna bother looking at it, so my question is how much of the frontend do i need to know in order to become a sucessfull backend developer??

reddit.com
u/TrickyTechnician911 — 13 days ago