-
Notifications
You must be signed in to change notification settings - Fork 47
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
Prune and compress images #53
Comments
This may be helpful, too It seems that there are a number of images that are not being used on the website that could be cleaned out. Maybe I'm just not seeing them? For example, the I'm working on #1 & #4 which will include running all the current images through imageoptim. |
@hagata, good to know. I think the work in #1 and #4 combined with using A CDN (https://en.wikipedia.org/wiki/Content_delivery_network) for the compiled assets in production will help the performance on slower clients, but that's probably best discussed in a separate issue. |
@heyellieday, Yeah, the work for the site performance won't solve this issue. |
Is this the same as this issue? |
@MichelleGlauser Yes, partially. #3 refers mostly to binary assets, but the root of the issue is the same as this. |
We still do not have a solution for this. |
There are really three issues here. Repo Is Too LargeI recommend we migrate to git-lfs to handle this problem. I can convert this repo to use LFS. Optimize ImagesThere's a number of ways to approach this, but the easiest is to probably just do it locally for now when there are new images. On the Mac, just use ImageOptim. We should make an effort to optimize an image before it's committed to the repo the first time. For vector art, such as icons and logos, we should migrate to SVGs when possible. Prune ImagesI don't think we want to remove images from the repo history altogether. Instead, we want to keep |
Upon pulling the repository for the first time, I noticed it was nearly 200mb in size:
I think that it would be beneficial to trim the assets stored in the repo, which on disk are roughly 48mb, but I am unsure if that would reduce the size of the repo when initially pulled, based on my initial research: http://stackoverflow.com/questions/8185276/find-size-of-git-repo
If reducing the size of assets store in the repo can reduce the initial size, then an option such as storing the large assets (mostly images) with a static storage provider like Amazon S3 might be worth looking into.
The text was updated successfully, but these errors were encountered: