benjaoming, 12 days ago

@nanorepublica Thanks for doing this write-up! Your part 1 and part 2 resemble my experience, too. Especially naming the project package simply project or django_project is something I've used the past years to avoid conflating the understanding with the custom application where 99% of logic lives.

If one was to take a "safe bet" at the inception of a project, I would go with "part 2" :)

benjaoming, 12 days ago

@nanorepublica I've also had projects as Python packages with everything under src/<acme>/:

src/acme  
src/acme/project # Django project  
src/acme/apps/users # User handling  
src/acme/apps/pages # Wagtail stuff  
src/acme/apps/events # Events stuff  

That way, we can do DJANGO_SETTINGS_MODULE=acme.project.settings which I think is nice :)

carlton, 14 days ago

@nanorepublica Nice series. You said to comment if you’d missed one… These days I almost always use the “Single Folder Layout”, where the project folder itself goes into INSTALLED_APPS, so you don’t have a separate app folder at all (but you’re also not in single file land)

https://noumenal.es/notes/django/single-folder-layout/

nanorepublica, 14 days ago

@carlton I believe that is the option I showed today! (I think?)

carlton, 14 days ago

@nanorepublica it is! Doh 🤦 I read it as the single file version, because I clicked the Will and Paolo link.

Carry on! 🎁

ghickman, 13 days ago

@carlton @nanorepublica this is my preferred layout too, even for medium sites. I should write up my thoughts on Django apps at some point 🤔

carlton, 13 days ago

@ghickman NOW! 😜

ghickman, 13 days ago

@carlton I knew you’d say that! Soon… maybe. I have a feeling it might be contentious 😬

carlton, 13 days ago

@ghickman I hope so. 🍿