@ghickman it's a bit of a click bait title, but the number of times someone new to Django has messed up their migrations by fiddling in an external tool... It's a clear 🤦 from me
I am still setting up my new laptop, I'm taking my time and also not trying to be overwhelmed by getting a proper dotfiles repo setup.
Three questions that come to mind:
Any recommendations for dealing with credentials (typically some form of API key) that live in config files that I would want to live in my dotfiles repo
Similarly for transferring SSH keys.
What do mac users do for local files that aren't in some form of git repo (pdfs, office files, etc) Migration Assistant?
I get the feeling like my idea might be packaging up a suite of existing hacks and tools
this unnamed codebase lacks any reasonable tests and I haven't yet pushed hard enough to make it a priority. Ideally I want to remove the cruft before I write them.
@CodenameTim@frank the thing that gets me, is that I have heard it said multiple times 'start a third-party package to see what traction and popularity it gets'
But I have only seen a single discussion/process about what constitutes enough popularity to get something into core Django or what that process could look like.
The optionality of third party packages is great, but having a process/documentation would be advantageous.
My assumption is that we lack usage numbers or a similar proxy as a metric or the process for saying a package is up for integration or not.
Or it could be a series of steps.
Create the package
Get it mentioned in the official docs
Then it can be voted on to be included in Django?
To reiterate, I am definitely not saying every package should get to be in Django but this is more a response to the feature proposals getting the feedback of 'make a package'
@carlton@frank@CodenameTim My original post was an idea of perhaps a halfway house to include packages into the core of Django.
But perhaps this is just a repackaging of the --template option on startproject
Idea: What #Django is for ORM, it could also be for HTTP APIs?
An immense amount of work has gone into shaping django-ninja (fantastic project) and experienced frameworks like DRF and FastAPI.. some patterns must surely be emerging that are mature enough to be bundled into Django itself?
@benjaoming I know that @carlton has been pushing for content negotiation to get into core as a first step so Django can natively process the likes of JSON etc.
Beyond that I'm not sure since there are a few good options out there. The forum/tickets would be the place to check for existing discussions