You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@airavata.apache.org by "Eroma (JIRA)" <ji...@apache.org> on 2017/04/04 19:56:41 UTC

[jira] [Updated] (AIRAVATA-2337) Organize Django source code in repositories

     [ https://issues.apache.org/jira/browse/AIRAVATA-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eroma updated AIRAVATA-2337:
----------------------------
    Issue Type: New Feature  (was: Bug)

> Organize Django source code in repositories
> -------------------------------------------
>
>                 Key: AIRAVATA-2337
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2337
>             Project: Airavata
>          Issue Type: New Feature
>            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)