From b10f7b69134207aa3dfbbf5e7922909d95123b39 Mon Sep 17 00:00:00 2001 From: Trevor Emerick Date: Wed, 8 Jul 2026 23:13:05 -0400 Subject: [PATCH] docs(php): fix sample app README vendor path Point build instructions at lib/vendor/ to match composer.json and clarify that build.sh is only required for offline staging. Co-authored-by: Cursor --- examples/cf-php-sample-app/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/cf-php-sample-app/README.md b/examples/cf-php-sample-app/README.md index 8bf4e7b5..2dba07c6 100644 --- a/examples/cf-php-sample-app/README.md +++ b/examples/cf-php-sample-app/README.md @@ -4,6 +4,6 @@ This App is an example of how to use the [Datadog Cloud Foundry Buildpack](https ## How to build and push -1. Run `./build.sh` to vendor Composer dependencies into a local `vendor/` folder so the app can be staged on offline Cloud Foundry environments. The `dd-trace-php` native extensions are provided by the Datadog buildpack itself once `DD_APM_INSTRUMENTATION_ENABLED=true` is set. +1. For offline Cloud Foundry environments, run `./build.sh` to vendor Composer dependencies into a local `lib/vendor/` folder so the app can stage without reaching packagist.org. Online environments can skip this step — `php_buildpack` runs `composer install` during staging. The `dd-trace-php` native extensions are provided by the Datadog buildpack itself once `DD_APM_INSTRUMENTATION_ENABLED=true` is set. 2. Update the `manifest.yml` file with any other extra configuration options. 3. Run `cf push --var DD_API_KEY= --var ENV=`, substituting `` with your Datadog API key value.