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
Provide more detailed output during CLI execution.
For example, running craft blitz/cache/generate-site 1, it would be great to see which pages are being processed at any given time. This would have the added benefit of providing a way to troubleshoot particularly lengthy generations, or exceptions that cause the command to fail. Ideally, these would be written directly to the CLI during execution so our deployment scripts would capture them as the output of the call. Below is a rough outline of the type of information that might be useful.
Additionally, running any CLI that combines multiple commands such as blitz/cache/refresh could output each step of the command being executed. Currently, the refresh command seems to hang with no output.
If the output would cause a slowdown in the execution of the command, it could be flagged on and off. Our preference would be not to hide it behind debug, but instead have it accept a flag of --verbose or something similar.
Plugin Version
No response
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion. I added a verbose output mode to blitz/cache console commands in 097dfc0 that can be activated by adding a --verbose flag. It doesn’t quite report everything in your outline, but it lists URLs as they are generated, noting any errors in red.
You can test this by running ddev composer require "putyourlightson/craft-blitz:dev-develop as 4.14.0".
Thanks @bencroker! I Just ran through a quick test, and the output is very helpful. I'll continue to test and let you know if anything pops up. Appreciate your quick attention to this request!
Feature Request
Provide more detailed output during CLI execution.
For example, running
craft blitz/cache/generate-site 1
, it would be great to see which pages are being processed at any given time. This would have the added benefit of providing a way to troubleshoot particularly lengthy generations, or exceptions that cause the command to fail. Ideally, these would be written directly to the CLI during execution so our deployment scripts would capture them as the output of the call. Below is a rough outline of the type of information that might be useful.Additionally, running any CLI that combines multiple commands such as
blitz/cache/refresh
could output each step of the command being executed. Currently, therefresh
command seems to hang with no output.If the output would cause a slowdown in the execution of the command, it could be flagged on and off. Our preference would be not to hide it behind debug, but instead have it accept a flag of
--verbose
or something similar.Plugin Version
No response
The text was updated successfully, but these errors were encountered: