Michael Slowik

I'm working on some solutions: - `opcache.enable=true` could be resolved per project with `php.dev.ini` + `.gcloudignore` that should ignore it during gcloud deployment. - composer could support env `COMPOSER_ARGS` or...

In case someone will need it, the solution for disabling opcache on local: - Create `php.local.ini` - Add to `php.local.ini` line `opcache.enable=false` - Add to `.gcloudignore` line `php.local.ini` This way...

PR to resolve composer related issues https://github.com/GoogleCloudPlatform/buildpacks/pull/219

I will make another PR that will check `DEV_MODE` flag instead. I would recommend adding an option to customize composer flags in the future anyway, mainly because of the possibility...

Ok. I saw considered `DEV_MODE` variable before but it appeared that option to customize `COMPOSER_ARGS` would be way more flexible.

I'm trying to make a PR for this but while running `go test` I get: ``` --- FAIL: TestDetect (0.01s) --- FAIL: TestDetect/without_composer.json (0.00s) buildpacktest.go:220: running command /Users/User/Code/sandbox/buildpacks/cmd/php/composer_gcp_build/var/folders/bp/07pr5qb11n990ygm6qfdqr3c0000gn/T/go-build2585455591/b001/composer_gcp_build.test -test.run=TestDetect/^without_composer.json$ -test.paniconexit0...

Perhaps I can add some more information on why this PR is important. AppEngine is a great tool in production but running apps locally was always complex. If you get...

`COMPOSER_ARGS` renamed to `GOOGLE_COMPOSER_ARGS`

I'm working on a possible solution and I'm wondering if the source of container running App Engine (PHP) is publicly available? Perhaps this functionality can be turned into a buildpack.

`-enable_iam_login` is not required anymore and should be dropped. `-enable_iam_login` might result in errors on MySQL (https://github.com/GoogleCloudPlatform/cloud-sql-proxy/issues/1436).