[
https://issues.apache.org/jira/browse/AIRAVATA-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798188#comment-16798188
]
Marcus Christie commented on AIRAVATA-2984:
-------------------------------------------
I've implemented setting the DEBUG flag to False. This does turn on caching and
it helps the issue.
However, if the webpack-stats.json file had not been loaded once then it won't
be cached and you can still run into the problem during a deploy.
To really address this I think we need to load the webpack-stats.json file out
of the static/ directory instead of from the source checkout directory. This
way everything is consistent. And this would allow us to set DEBUG to True if
we needed to do so.
> 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)
