Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cleanup of old Ghost versions

See original GitHub issue

Opening this issue for discussion and ideas.

Currently whenever a Ghost installation is updated using the CLI, the old version is left in the versions folder so that the user can rollback to the previous version should something go wrong. However, none of the older versions beyond that one previous version are ever cleaned up. My initial thought is that Ghost-CLI should keep 1 (maybe 2) previous releases just in case, and on update clear out anything older than that, but am curious if there’s any other use-cases for keeping more than 2 versions around that I haven’t thought about.

Issue Analytics

State:
Created 6 years ago
Comments:8 (6 by maintainers)

Top GitHub Comments

1reaction

acburdinecommented, Jun 21, 2020

what we might be able to do is reduce the number of old versions we keep. right now we keep 5 but we could reduce that to 2 maybe, since we can always reinstall older versions.

1reaction

ghostcommented, Sep 24, 2018

Is it safe to manually delete older versions? I’ve only got the last 4 versions installed and it’s chomping through a massive 622Mb of disk space:

158M    ./2.0.3
155M    ./1.25.3
155M    ./1.25.5
155M    ./1.24.9

The size of node_modules is insane - when a new version is installed, could this not be cleaned out, and then if rolled back, it could be “npm install-ed” again?