[
https://issues.apache.org/jira/browse/AIRAVATA-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943084#comment-16943084
]
ASF subversion and git services commented on AIRAVATA-2984:
-----------------------------------------------------------
Commit 6e2cc65eaaf2ebfee1fc081a3a996199533babad in airavata-django-portal's
branch refs/heads/master from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=6e2cc65 ]
Revert "AIRAVATA-2984 Generate webpack files in STATIC_ROOT dir"
This reverts commit 22134a0b5b30c09af6d0fdaf2add142beaedf83b.
> Webpack bundle fails to load during deploy
> ------------------------------------------
>
> Key: AIRAVATA-2984
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2984
> Project: Airavata
> Issue Type: Bug
> Components: Django Portal
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
> Fix For: 0.19
>
>
> {noformat}
> Loading failed for the <script> with source
> “https://beta.gateway.simvascular.org/static/django_airavata_admin/dist/js/app.d5795752.js”.
> {noformat}
> The problem I believe is that Django's webpack-bundle-tracker is bundle
> information from the new webpack-stats.json file that is created during the
> build, instead of the webpack-stats.json file that is in the /static/ assets
> directory. The new webpack-stats.json isn't put into the /static/ assets
> directory until everything is built and {{./manage.py collectstatic}} runs.
> webpack-bundle-tracker should be configured to read the webpack-stats.json
> file from the /static/ assets directory instead.
> h2. TODO
> - [x] Allow production deployments to override the locations of the
> webpack-stats.json files and set them to their static directory locations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
