GitHub Actions cache has a number of issues surrounding performance when used on self-hosted runners. GitHub has failed to address this on numerous occassions so BuildJet created their own free cache alternative with double the amount of storage and much faster performance. It would be nice if we could use this in ramsey/composer-install, providing an option to specify which cache we wanted to use.
Proposal/solution
I propose that we add a new option which specifies which cache we would like to use and have this shared action then use the cache specified. We can leave the default to GitHub to keep backward compatibility.
Background/problem
GitHub Actions cache has a number of issues surrounding performance when used on self-hosted runners. GitHub has failed to address this on numerous occassions so BuildJet created their own free cache alternative with double the amount of storage and much faster performance. It would be nice if we could use this in
ramsey/composer-install, providing an option to specify which cache we wanted to use.Proposal/solution
I propose that we add a new option which specifies which cache we would like to use and have this shared action then use the cache specified. We can leave the default to GitHub to keep backward compatibility.
Additional context
https://buildjet.com/for-github-actions/blog/launch-buildjet-cache