Is it better to create repositories at a site-, project- or app-level?
In other words, if I implement the conventional[1] directory structure
below, is it better to place the entire site (example.com) under a
single git repository, or would it be wiser to create separate git
repos for each custom app?
Any suggestions on the best course of action (Perhaps something to add
to the conventions list)?
example.com/
settings.py
urls.py
local_apps/
custom apps written for this project (Preferably Reusable;
Probably on your PYTHONPATH)
external_apps/
External reusable apps you are using on this project
Note: These apps can also live anywhere on your PYTHONPATH
projects/
dev_example/
production_example/
django96_example/
manage.py, settings, urls, etc
docs/
This will hold the documentation for your project
static/
-In production this will be the root of your MEDIA_URL
css/
js/
images/
tests/
- Project level tests (Each app should also have tests)
uploads/
- content imgs, etc
templates/
- This area is used to override templates from your reusable
apps
flatpages/
comments/
example/
app1/
app2/
[1] http://ericholscher.com/projects/reusable-app-docs/projects/overview.html
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
