Carl, why not have django-admin.py startproject create a site_root directory
and
within it a project_root directory by default if issued from within e.g.
example.com (the outermost container/directory e.g. a virtualenv):
example.com <-- mkvirtualenv example.com; non-Python stuff somehow
related to this project
sass
tmp
gems
...
site_root <-- django-admin.py startproject; on sys.path from
here down; Python stuff
.git <-- git init (or hg init or whatever)
.gitignore
manage.py
sqlite3db
...
project_root <-- django-admin.py startproject; Django stuff
specific to this project
__init__.py
settings.py
urls.py
...
django-admin.py startproject would create site_root and project_root
put as this patch intends, one could always easily rename site_root to
whatever he wants. example.com is entirely decoupled anyway and can be
named anything.
Maybe it is not bad having project_root as a fix name at this location
in the filesystem tree as it makes it easy to reference things -- not
just for people but also scripts and such. I am generally against to
much rules/conventions but in this case I think having some fixed name
at a fixed location would make things easier (even if it is just for
new people to grasp things).
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/pVCDd7qP2ucJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
