-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
Investigate & Document installation on Heroku #46
Comments
There is a predefined list of extensions that can be enabled through composer.json https://devcenter.heroku.com/articles/php-support#extensions I think the only way at the moment would be to build a custom buildpack for heroku, more here heroku/heroku-buildpack-php#235 (comment) |
Indeed; I've just verified it doesn't work out the box:
and
|
Here's me thinking "there must be a better way".... heroku/heroku-buildpack-php#377 |
I prepared a branch to (ref: https://github.com/heroku/heroku-buildpack-php/compare/master...asgrim:add-scoutapm-ext?expand=1) |
Thanks for the effort, let me know once it's open so we can organize another "thumbs up" campaign to speed things up ;) |
Note: the newly released scout-apm-php version 2.1.1 (and underlying CoreAgent 1.2.7) solves the mentioned issue with the extension + spans happening too early. |
Submitted patch to add |
It's important that we can support Heroku deploys of our agent fully, which includes this native extension.
It seems probable that adding
"ext-scoutapm": "*"
to composer.json will "just work", but we need to try it, and then document it here and in Scout's docs.The text was updated successfully, but these errors were encountered: