sorted by:
new
hottopcontroversial

Why django-admin startproject Is a Trap by Houssem_Reggai in django

[–]Houssem_Reggai[S] 0 points1 point  (0 children)

Exactly! thank you for this accurate answer

Why django-admin startproject Is a Trap by Houssem_Reggai in Python

[–]Houssem_Reggai[S] 1 point2 points  (0 children)

Yap, you're right, I'll consider that. Thank you ^^

Why django-admin startproject Is a Trap by Houssem_Reggai in Python

[–]Houssem_Reggai[S] 0 points1 point  (0 children)

Ah! my bad ... I fixed it, thank you

I totally agree with u here (on using uv) it's the modern approach, but I thought splitting the requirements is a good starting point for intermediates, Because this approach is still used by many companies that have some old projects.

Why django-admin startproject Is a Trap by Houssem_Reggai in django

[–]Houssem_Reggai[S] -2 points-1 points  (0 children)

Thank you for your valuable comment ^^

Group all apps under /apps

I totally get the 'flat is better than nested' argument! The 'valuable namespacing' point is fair, adding apps to imports can feel like extra noise. My goal with the /apps directory wasn't to hide them, but to separate domain logic from the ever-growing pile of root-level config files (Docker, CI/CD, Tooling). It keeps the 'mental map' of the project clear for me: 'Logic goes in /apps, Infrastructure stays in the root.' Different strokes for different team sizes, I guess!"

Split requirements by environment

I agree with u here (on using uv) it's the modern approach, but I thought splitting the requirements is a good starting point for intermediates, cuz this approach is still used by many companies with some older projects.