I don't understand why it still tries to access composer.lock file in PHP (classic) mode.
Any solution please?
Sending build context to Docker daemon 30.13 MB
Sending build context to Docker daemon
Step 0 : FROM tutum/buildstep
# Executing 3 build triggers
Step onbuild-0 : RUN mkdir -p /app
---> Using cache
---> 017db600a83a
Step onbuild-1 : ADD . /app
---> 559c0fdcff9c
Step onbuild-2 : RUN /build/builder
---> Running in a7c495eb6d6d
PHP (classic) app detected
-----> Bundling NGINX 1.4.4
-----> Bundling PHP 5.5.9
-----> Bundling extensions
apcu
phpredis
mongo
/build/buildpacks/heroku-buildpack-php/bin/../frameworks/silex: line 7: /build/app/composer.lock: No such file or directory
/build/buildpacks/heroku-buildpack-php/bin/../frameworks/slim: line 7: /build/app/composer.lock: No such file or directory
/build/buildpacks/heroku-buildpack-php/bin/../frameworks/symfony2: line 8: /build/app/composer.lock: No such file or directory
/build/buildpacks/heroku-buildpack-php/bin/../frameworks/zf2: line 7: /build/app/composer.lock: No such file or directory
-----> Setting up default configuration
! Lockfile required. Please check it in.
2014/07/13 19:54:59 The command [/bin/sh -c /build/builder] returned a non-zero code: 1
Hi,
I don't understand why it still tries to access composer.lock file in PHP (classic) mode.
Any solution please?
Thx!