Skip to content
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

Add Blackfire.io support #12

Merged
merged 2 commits into from
Sep 24, 2019
Merged

Add Blackfire.io support #12

merged 2 commits into from
Sep 24, 2019

Conversation

navarr
Copy link
Member

@navarr navarr commented Sep 11, 2019

In order to trigger Blackfire build, .env file must contain WARDEN_BLACKFIRE=1

The following env variables should be set for Blackfire:

  • BLACKFIRE_CLIENT_ID
  • BLACKFIRE_CLIENT_TOKEN
  • BLACKFIRE_SERVER_ID
  • BLACKFIRE_SERVER_TOKEN

@Shero-Inc
Copy link
Contributor

+1 this would be perfect.

In order to trigger Blackfire build, .env file must contain WARDEN_BLACKFIRE=1

The following env variables should be set for Blackfire:

- BLACKFIRE_CLIENT_ID
- BLACKFIRE_CLIENT_TOKEN
- BLACKFIRE_SERVER_ID
- BLACKFIRE_SERVER_TOKEN
@davidalger davidalger changed the base branch from master to develop September 23, 2019 18:21
@davidalger
Copy link
Collaborator

Tested this locally by adding the following to a .env.blackfire file in my project root (since .env is committed to the repo in my test case):

export WARDEN_BLACKFIRE=1
export BLACKFIRE_CLIENT_ID=<my_id>
export BLACKFIRE_CLIENT_TOKEN=<my_token>
export BLACKFIRE_SERVER_ID=<my_id>
export BLACKFIRE_SERVER_TOKEN=<my_token>

Then ran source .env.blackfire followed by warden env up -d to configure the blackfire-agent and php-blackfire containers. Worked flawlessly. You rock!

Need to update the README with some information on Blackfire support and this will be ready to merge and include in the next published release version.

davidalger added a commit that referenced this pull request Sep 24, 2019
@davidalger davidalger merged commit eb09967 into wardenenv:develop Sep 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants