Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit2d2e274

Browse files
committed
[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 adifferent 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 isgenerated. So the application is quite slow in dev env. And for peopleon MacOSX (with docker) is a big pain! And obvisouly, this neverstabilizes !This occurs a lot when you have a worker, that crash and reboot in thebackground, and you browse the web interface. Or when you have somethingthat hit your API every X secondes, and you are working on a worker.
1 parent04b9ce3 commit2d2e274

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎src/Symfony/Component/Config/Resource/ComposerResource.php‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ public function isFresh($timestamp)
4848
{
4949
self::refresh();
5050

51-
returnself::$runtimeVendors ===$this->vendors;
51+
returnarray_values(self::$runtimeVendors) ===array_values($this->vendors);
5252
}
5353

5454
/**

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp