-
Notifications
You must be signed in to change notification settings - Fork 2
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
Composer caching is broken #9
Comments
Oh! Nice shot! By the way, I worked on the future main concepts of module injection in a separated app... It will be merged in the buildpack soon :-) |
great. |
See Incenteev/heroku-buildpack-sdz@5a716ad for the way I fixed it in our buildpack |
Yeah I just tested the same thing on the buildpack in Python, but it doesn't seems to work. I'll try to work on it tomorrow. |
well, for me, it works. Check whether you don't have another part overriding it too. |
I ported the composer caching back to our bash buildback based on the old SimpleIT repo. And this allowed me to spot an issue when deploying: your cache is never used as you delete it before that.
the issue is that the composer cache is in
self._bp.cache_dir+'/www/vendor'
but you useself._bp.cache_dir + '/www'
as temporary folder when isolating the app filesThe text was updated successfully, but these errors were encountered: