You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by manuelson September 7, 2023
When you launch the command warden blackfire run {command} blackfire gives you the option to add the --env parameter.
Warden should support a new global variable on .env file (e.g. BLACKFIRE_ENV_ID) by editing the .cmd commands/blackfire.cmd it should accept the --env parameter as documented by blackfire (https://blackfire.io/docs/profiling-cookbooks/profiling-cli)
The text was updated successfully, but these errors were encountered:
Discussed in https://github.com/orgs/wardenenv/discussions/697
Originally posted by manuelson September 7, 2023
When you launch the command warden blackfire run {command} blackfire gives you the option to add the --env parameter.
Warden should support a new global variable on .env file (e.g. BLACKFIRE_ENV_ID) by editing the .cmd commands/blackfire.cmd it should accept the --env parameter as documented by blackfire (https://blackfire.io/docs/profiling-cookbooks/profiling-cli)
The text was updated successfully, but these errors were encountered: