You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Marcus Christie (JIRA)" <ji...@apache.org> on 2019/04/10 18:37:00 UTC
[jira] [Updated] (AIRAVATA-2984) Webpack bundle fails to load
during deploy
[ https://issues.apache.org/jira/browse/AIRAVATA-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Christie updated AIRAVATA-2984:
--------------------------------------
Description:
{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.
was:
{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
- [ ] Allow production deployments to override the locations of the webpack-stats.json files and set them to their static directory locations.
> 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.
> 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
(v7.6.3#76005)