Via https://indiehackers.social/@nanorepublica/112909832749194692

Via https://mastodon.social/@EmmaDelescolle/112650193871139643

Via https://mastodon.cloud/@radiac/112641898082821618

In my experience flask is great until it isn't - I've seen quite a few projects which outgrew it, and the lack of django's batteries and guard rails left a maintenance nightmare. Not sure if it'll be helpful, but as a result I wrote nanodjango, which lets you write a django site in a single file, then convert it to a full project if you outgrow it.

DEFNA: Django Events Foundation North America

Via Django News #238

Via https://mastodon.social/@gcollazo/112606165516489513

Via Don't use pgAdmin (or similar tools)

I've used django CMS for a few projects and I'm quite happy with it. I've been wondering what wagtail has to offer that sets it apart from django CMS. I installed it some time ago but didn't dive very deep.

So what are the strengths and weaknesses of both systems?

DEP-0014: https://github.com/django/deps/blob/main/accepted/0014-background-workers.rst Reference implementation: https://github.com/RealOrangeOne/django-tasks Author: https://mastodon.theorangeone.net/@jake

I ran across this while looking for tools to provide something like the raw_id_fields widget in Django's list admin view. This post is a few years old at this point, but I think the solution it contains still works pretty well (caveat: I haven't tried it yet).

I also enjoyed the author's take on the conversation with support. I can definitely relate to that.

This article is several months old, but if you're like me and missed some of the new changes, it was a nice surprise, with things like generated fields and fields with database default values (as opposed to the existing Python default values).

Via Django News #225

Also via Django News #224

The code: https://github.com/jasongi/collectfasta

Via the excellent Django News #224