-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Blackfire: tests, agent v2, separate agent package, blackfireio/integration-heroku buildpack support #488
Conversation
all env vars are shared between agent and extension, with the exception of the socket (BLACKFIRE_SOCKET vs BLACKFIRE_AGENT_SOCKET) we are hard-coding the log file and agent socket values to ensure the basics always work; passing the socket directly to the agent
if users have https://github.com/blackfireio/integration-heroku set as a buildpack that runs before ours, use that instead of our own package
f638c49
to
79f4553
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you have the possibility to automatically download the latest version of Blackfire extension of needed?
We can't do that for compliance reasons, unfortunately - released versions must be fixed and mirrored by us for audit log purposes. Longer-term, I guess the best solution is for us to simply not provide the CLI at all, but it'd be great if the user experience was reasonable in that case (i.e., meaningful error message instructing folks to install your buildpack). Of course, another solution would be for you to also provide the extension packages ;) We can tackle that after I migrated the platform installer plugin to Composer v2. |
OK understood. |
Until now, the
ext-blackfire
extension also always bundled theblackfire-agent
program. That program relays telemetry from a language runtime to the Blackfire servers in the background.This PR: