[
https://issues.apache.org/jira/browse/AIRAVATA-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778656#comment-16778656
]
Marcus Christie commented on AIRAVATA-2984:
-------------------------------------------
Another approach would be to have django-webpack-loader cache the stats info,
which it does by default if DEBUG is False:
https://github.com/owais/django-webpack-loader#cache
So another fix would be to set DEBUG to False in settings_local.py, [which
we're not currently
doing|https://github.com/apache/airavata/blob/develop/dev-tools/ansible/roles/django/templates/settings_local.py.j2#L38].
> 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
>
> {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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
