-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Large staticfiles directory #7
Comments
If you use for example
A version of these files is built for each release. They are independent between versions. |
@Aleksi44 I already fixed this issue in my project by class MyStaticFilesConfig(StaticFilesConfig):
ignore_patterns = [
"*wagtailyoast/*0.0.1*",
"*wagtailyoast/*0.0.2*",
"*wagtailyoast/*0.0.3*",
"*wagtailyoast/*0.0.4*",
"*wagtailyoast/*0.0.5*",
"*wagtailyoast/*0.0.6*",
"*wagtailyoast/*0.0.7*",
"*wagtailyoast/*0.0.8*",
] but it seems very ugly and I will have to keep it in mind when updating to next releases. Is there any reason, why it is needed to have the old versions in current distribution? |
You are not supposed to have all these files. If you delete your
Do you still have all those files? I use a new file name for each release to avoid cache problems. |
These files are in the PyPI package. |
Sorry for this late reply. |
@Aleksi44 Thank you very much. |
@Aleksi44 It seems that in version |
In the
static/wagtailyoast/dist
directory there are js/css files for all the versions (0.0.1 - 0.0.9). Especially theyoastanalysis0.0.x.js
andyoastworker0.0.x.js
files are quite large and having them 9x makes the whole directory to be 39 MB large.This slows down the whole collectatic process for my application (I use whitenoise with static files compression) and makes the distribution package unnecessarily huge and slows down the whole deplyment process.
Are the old versions of those libraries really needed?
The text was updated successfully, but these errors were encountered: