Via https://fosstodon.org/@adamchainz/114296390441362261

i'm completely new to the django eco system, coming from flask.

what i want (and don't know how to accomplish) is to put some restrictions to a set of urls: x/<uuid>/images x/<uuid>/imageupload and others should only work, if uuid can be found in the database and is still valid.

in flask i would probably use a blueprint, but this concept does not seem to exist in django, right?

what i like about the blueprint concept is, that it's not possible to add a url under the x/<uuid> "namespace" and forgetting about the auth mechanism, as this is handled for all urls in the blueprint.

how would you handle this in django?

i've already learned about apps and a custom middleware, but this looks quite complicated on first sight? as the middleware always intercepts all requests, and i would have to check on my own if this is a request to x/<uuid>?

i've also looked at existing apps, and [django-rq uses the statt_member_required decorator](https://github.com/rq/django-rq/blob/fe539b6

via https://indieweb.social/@adamghill/114115517598594251

via https://mastodon.social/@openrisk/114103439082745531

via https://hachyderm.io/@kevinrenskers/114072304000264553

via https://fosstodon.org/@laymonage/114014338677264240

via https://django-news.com/issues/272

For those who have been following or been involved with recent development of Ninja, you’ll notice that for about a year, almost all development has come to a halt. About 50 PRs have built up on the GitHub repository, many of which fix crucial issues, but are not getting any feedback and have no path forward to getting them merged. PRs that fix documentation will get merged in a day, but most PRs that touch code are left out to dry. Among these PRs include performance improvements, the validation vs. serialization split, my own fix for aliases, and much more. It's getting desperate enough that people are posting monkeypatches in the PRs.

I have spoken with Ninja's maintainer a bit about the issue and I think it's mostly just a split in priorities between him and myself. That's totally reasonable and respectable, its his project. But as a user of the library, I can't really say that I feel supported by this direction, and I would assume from the many repeated requests for revi

via https://mastodon.social/@python_discussions/113945835385715022

also check: The Key Benefits of Using a NoSQL Database in Django Development via Django News
and Official Django MongoDB Backend - Jib Adegunloye | Django Chat

via https://django-news.com/issues/270

via https://hachyderm.io/@kevinrenskers/113883446564707203

via https://fosstodon.org/@gagliardi_vale/113879003550726821