Skip to content
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

Purge unreferenced image files #115

Open
abrock opened this issue Mar 23, 2015 · 2 comments
Open

Purge unreferenced image files #115

abrock opened this issue Mar 23, 2015 · 2 comments

Comments

@abrock
Copy link
Member

abrock commented Mar 23, 2015

Here is a list of file not referenced by any file in the repository, found by this script and cross-checked against a complete download of raumzeitlabor.de.

A lot of files are scaled versions of large images used by Wordpress but not used by the current setup. Purging these from the repo history would free roughly 95,448,311 bytes.

The list still needs work, as there are false positives in the list, e.g. else.png which is definitely used but only referenced via something I didn't trace down yet (CSS|JS?). It might be safe to purge every listed file within assets/uploads but I can't guarantee that atm.

@elsbrock
Copy link
Collaborator

Interesting. Most of the images in assets/uploads I'd assume I just copied with the last commit. So before doing any other commit, let's get rid of them and do a push --force to decrease the repo size.

The stuff in assets/avatars is referenced by the blogpost template in app/_includes/blogpost.html and depends on the username that is given in the YAML frontmatter.

elsbrock added a commit that referenced this issue Mar 24, 2015
These files are included in our repository but referenced nowhere.

closes #115
@tabascoeye
Copy link
Member

@abrock want to restart this effort on a branch with a PR? (those get built and deployed, so you can see if the website still works...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants