I’m not sure whether this belongs in the Github thread or here or somewhere else, but one possible compromise on something like this would be if there were handful of “official” startproject templates that were well-maintained and referred to in the docs. These could be maintained by Django or by third parties. But basically the idea being that we can at least recommend a few other options if there is not ever going to be enough momentum to improve on the default one.
1 Like
I know I’m very late to the party but I still use the naming convention from your book Django for Beginners. A top level directory which is the name of the project and then startproject config .
Yes, you do have to adjust a little to allow that wsgi.py etc are in a different folder from where most documents say they will be but it’s not that difficult. I did find the nested folders confusing when I started and redundant.
What I do find helpful too is your idea of commenting the name of the file in the file itself while I’m working, I do worry though that if I go live if that’s a security issue?
Not in the least.
Unless you’re doing something seriously wrong, your project files aren’t directly exposed to the web. (If those files are, then you’ve got more important issues to worry about than just the file names.)
2 Likes
Hello,
I’ve prepared a DEP with the changes I discussed early in this thread. I think at this point it’s in a reasonable place to review: Add draft for extended project template by knyghty · Pull Request #98 · django/deps · GitHub
1 Like