[jira] [Updated] (AIRAVATA-3017) Build the JS code before deploying to each portal

["Marcus Christie (JIRA)" <ji...@apache.org>]

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

Marcus Christie updated AIRAVATA-3017:
--------------------------------------
    Description: 
The Ansible deploy builds the JS frontend code for each portal deployed.  This is a lot of duplicated effort when deploying multiple instances of the Django Portal to a web server.

Ideally we would build the JS frontend code once and then copy it to the deployment of each Django Portal instance.

Some things to keep in mind:
* the webpack-stats.json files generated by webpack-bundle-tracker and used by django-webpack-loader have full file paths and these paths are currently specific to each instance
* possibly we could have portals share static directories instead of each having their own

> Build the JS code before deploying to each portal
> -------------------------------------------------
>
>                 Key: AIRAVATA-3017
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3017
>             Project: Airavata
>          Issue Type: Project
>            Reporter: Marcus Christie
>            Priority: Major
>
> The Ansible deploy builds the JS frontend code for each portal deployed.  This is a lot of duplicated effort when deploying multiple instances of the Django Portal to a web server.
> Ideally we would build the JS frontend code once and then copy it to the deployment of each Django Portal instance.
> Some things to keep in mind:
> * the webpack-stats.json files generated by webpack-bundle-tracker and used by django-webpack-loader have full file paths and these paths are currently specific to each instance
> * possibly we could have portals share static directories instead of each having their own



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)