webbower

Well, that solves some major hair pulling. Thanks for the tip on -E @guttmann and all the attention @nightjarnz. I probably owe you quite a few beers for all the help you’ve given me

👍 (1) 🤷 (1) 👍 (1)
webbower

The containers are snapshots of a ready-to-go version of the app inside so I can’t really configure one to run with the dev autoload files since the same container is used for automated testing and deployment in our pipeline

webbower

Also, for building the containers, I run composer dumpautoload --no-dev and I apparently need to composer dumpautoload; phpunit; composer dumpautoload --no-dev in order to get the autoloader to see the test files

webbower

Ya. I ran into weirdness with users when running sake commands. 2 manifest caches would be created depending on how I flushed. If I flushed via browser, I’d get a manifest cache for the www-data user. If I flushed via sake, I would get a manifest cache for the VM user.

webbower

Ah. Didn’t know about the -E option. Going to try adding that

webbower

Oh wait. I wrapped the phpunit call in a composer script field and I forgot that I’m running it as sudo -u www-data -- ... 🤦

webbower

Pretty sure. Not sure how running $ foo.php and $ phpunit would differ users