-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Remove large and unneeded resources #6437
Conversation
Those assets are handled by bower, so if someone updates packages they will appear again |
I'm not sure we're doing that often |
I could add a .gitignore to the SonataCoreBundle directory excluding these files so they will never be committed again. |
I like this idea, WDYT @jordisala1991 ? |
Also add a .gitignore file to prevent these files from being added again
I've added the .gitignore file. |
Thank you @jorrit |
Subject
I am trying to optimize the size of my Docker container and a quick review using WinDirStat gave some surprising large files in src/Resources/private/SonataCoreBundleAssets/vendor:
These files are copied to public on
assets:install
so they count twice if sym/hardlinking is not available. I think that these files are unnecessary under any circumstance and can be removed without breaking the backwards compatibility promise. Many more files could be removed, but the ones above are the largest by a wide margin.I am targeting this branch, because no user should depend on these files.
Changelog