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
I'm setting up a deployment process using capistrano to publish a new version to a production server.
But when running for example the setup:static-content:deploy script, we get a lot of lines in our output, like this snippet:
An option to get rid of the progress would be handy to keep the output a bit more clean. I do like the information messages, so only the '.' output should be removed by that switch.
I know there is a --quiet switch, but this won't output anything at all.
So something similar as composer uses: --no-progress: Removes the progress display that can mess with some terminals or scripts which don't handle backspace characters.
Possible command candidates:
setup:di:compile
setup:di:compile-multi-tenant
setup:static-content:deploy
...
I'm most likely forgetting some
Thanks!
The text was updated successfully, but these errors were encountered:
hostep
changed the title
Feature request: A '--no-progress' switch for certain cli commands would be nice
Feature request: a '--no-progress' switch for certain cli commands would be nice
Dec 31, 2015
Hi guys
I'm setting up a deployment process using capistrano to publish a new version to a production server.
But when running for example the
setup:static-content:deploy
script, we get a lot of lines in our output, like this snippet:An option to get rid of the progress would be handy to keep the output a bit more clean. I do like the information messages, so only the '.' output should be removed by that switch.
I know there is a
--quiet
switch, but this won't output anything at all.So something similar as composer uses:
--no-progress: Removes the progress display that can mess with some terminals or scripts which don't handle backspace characters.
Possible command candidates:
I'm most likely forgetting some
Thanks!
The text was updated successfully, but these errors were encountered: