airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AIRAVATA-2934) Dynamically load Django apps into the Django portal
Date Wed, 27 Feb 2019 20:51:00 GMT


ASF subversion and git services commented on AIRAVATA-2934:

Commit 31a17e4eb8b20ec27b77aefcde2a6eb9a3c42b35 in airavata-django-portal's branch refs/heads/master
from Marcus Christie
[;h=31a17e4 ]

AIRAVATA-2934 Dynamically load custom Django apps using entry_points

> Dynamically load Django apps into the Django portal
> ---------------------------------------------------
>                 Key: AIRAVATA-2934
>                 URL:
>             Project: Airavata
>          Issue Type: Bug
>          Components: Django Portal
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
> Develop a mechanism for automatically including Django apps that are installed in the
Django portal's virtual environment.
> The mechanism that seems most promising is to make use of entry points which I [wrote
about in this blog post|].
The entry point could register the AppConfig object of the Django app.
> This would allow the Django portal to:
> * loop over these Django apps and add them to INSTALLED_APPS in
> * add these apps to the url mappings
> In addition there is some metadata what would be useful for the AppConfig to provide:
> * {{url_home}} - the home url of the app so that it can be linked to. In builtin Django
apps in the Airavata portal, this is used to build the links to the various apps.
> * {{app_order}} - the order of the app in dynamically built list of apps
> * {{fa_icon_class}} - FontAwesome icon class to use for the app
> * {{app_description}} - Longer description of the app
> This metadata would be in addition to [{{name}}, {{label}} and {{verbose_name}}, which
are built in properties of AppConfig|].
> Probably for a future issue, but here are some additional concerns:
> * Django apps that integrate with the portal should use templates that extend [base.html|]
> * How to handle building JS code if the Django app requires a build step?  Perhaps could
be part of running {{python install}}?
> * Have the AppConfig provide metadata for populating the left hand side navigation in
the Django portal

This message was sent by Atlassian JIRA

View raw message