You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently using pipeline in a production environment and having the following issues. After collectstatic is run with every new deployment and with PIPELINE_ENABLED set to true, using pipeline to output js files in the templates generates two different source files; one file with an appended hash and the original file without the hash.
Both files exist in the static root folder but shouldn't cached storage produce the url for the latest version only. I have noticed that the duplicated files are ones not specified explicitly in the javascript section of the pipeline dict but are collected using directory wildcards e.g 'js/vendor/*.js'
Is there an explanation for this behaviour?
The text was updated successfully, but these errors were encountered:
Currently using pipeline in a production environment and having the following issues. After collectstatic is run with every new deployment and with PIPELINE_ENABLED set to true, using pipeline to output js files in the templates generates two different source files; one file with an appended hash and the original file without the hash.
Both files exist in the static root folder but shouldn't cached storage produce the url for the latest version only. I have noticed that the duplicated files are ones not specified explicitly in the javascript section of the pipeline dict but are collected using directory wildcards e.g 'js/vendor/*.js'
Is there an explanation for this behaviour?
The text was updated successfully, but these errors were encountered: