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.

Sign up for GitHub

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

Jump to bottom

[Config] Do not use absolute path when computing the vendor freshness #32579

Merged
merged 1 commit into from Jul 18, 2019
Merged

[Config] Do not use absolute path when computing the vendor freshness #32579

merged 1 commit into from Jul 18, 2019

Commits on Jul 17, 2019

  1. [Config] Do not use absolute path when computing the vendor freshness 

    When one uses Docker with a different mounting point between CLI & FPM,
the cache keeps regenerating because the ComposerResource class see a
different path for each SAPI. For example `/home/app/app/vendor` vs
`/var/www/app/vendor`.
So if you hit FPM, then the CLI, then FPM, each time a new cache is
generated. So the application is quite slow in dev env. And for people
on MacOSX (with docker) is a big pain! And obvisouly, this never
stabilizes !

This occurs a lot when you have a worker, that crash and reboot in the
background, and you browse the web interface. Or when you have something
that hit your API every X secondes, and you are working on a worker.
    @lyrixx
    lyrixx committed Jul 17, 2019
    Copy the full SHA
    2d2e274 View commit details
    Browse the repository at this point in the history