Adds commands for showing container logs

[comzeradd]

Some additional housekeeping commits.

Testing

npm run logs
npm run logs:php
npm run logs:mysql

[mardelnet]

Thanks for this, @comzeradd
I added this piece of code (error_log( 'Debugging is active!' );) to the functions.php file but I cannot see it logged in the terminal. Am I missing something?

[mardelnet]

Is env:usage no longer needed?

[comzeradd]

It's still there, but now is usage since it's a generic command. See 1d4564d

[comzeradd]

I added this piece of code (error_log( 'Debugging is active!' );) to the functions.php file but I cannot see it logged in the terminal. Am I missing something?

Hm.. yes that won't work. error_log doesn't send this out to the container logs. Probably xdebug would be more useful for things like that.

I didn't test with error_log, but when DEBUG is on certain errors and messages appear directly in the frontend. Even printing out variable values with var_dump.

[mardelnet]

I added this piece of code (error_log( 'Debugging is active!' );) to the functions.php file but I cannot see it logged in the terminal. Am I missing something?

Hm.. yes that won't work. error_log doesn't send this out to the container logs. Probably xdebug would be more useful for things like that.

I didn't test with error_log, but when DEBUG is on certain errors and messages appear directly in the frontend. Even printing out variable values with var_dump.

Thanks, @comzeradd
The PR greenpeace/planet4-master-theme#2495 is particularly hard to debug by printing out variables because AJAX is involved, sometimes the page reloads after completing the process, etc. So I need a way to log variables during the entire process and not only at the end of it.
I've never used it xdebug before. I'll give it a try.