[
https://issues.apache.org/jira/browse/AIRAVATA-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953607#comment-15953607
]
Marcus Christie commented on AIRAVATA-2337:
-------------------------------------------
I've now organized the source code like so
* there is a main folder, called {{django_airavata}}, that holds the
settings.py, etc.
* there is a package in this main folder, {{django_airavata.app}} that holds
all of the Django apps
Some snags:
* because of the way template lookup works in django, I decided to keep apps'
template folders with having more fully qualified names. For example, instead
of auth/templates/auth/auth_error.html, I instead have
auth/templates/django_airavata_auth/auth_error.html. Django will look up
templates by the name 'django_airavata_auth/auth_error.html' across all apps
and having a more fully qualified name should prevent picking up duplicates in
other packages.
> Organize Django source code in repositories
> -------------------------------------------
>
> Key: AIRAVATA-2337
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2337
> Project: Airavata
> Issue Type: Bug
> Reporter: Marcus Christie
> Assignee: Marcus Christie
>
> A Django project is made up of many different Django apps. How best to
> organize this in source control?
> My initial thought is to have a repo per app as well as a repo for kind of a
> template Django PGA making use of those apps. This way the template repo can
> be cloned and customized as needed for particular Django PGA instances, like
> the GeoGateway.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
