It seems that any modification of output, even though a single space char, will break the script.

some obfuscators are able to distinguish whether the strings (especially at the beginning) is a statement or not. This way, we can insert doc comment, most importantly which contains copyright, agreement, or other non technical info. Project which contains these info in every files are common today

Validate content-type on request Accept header (Content Negotiation) to allow only your supported format (e.g. application/xml, application/json, etc) and respond with 406 Not Acceptable response if not matched.

I had to autorize again because the domain changed.
And during that I noticed the site verification in the Google console is not mentioned. I think it is helpfull to add this step to the instruction.
Further it works fine.

The command allows wrapping /bin/bash per project to selectively running commands in containers

It should be included in regular output, like others. e.g.

source dotenv/load.sh
./scripts/util/exec.sh - <<SCRIPT
> echo Working dir: && pwd
> SCRIPT

Usage examples:

• phapp exec ls → always run in app environment, it should have the correct working dir
• phapp exec → opens shel