At the moment, I'm bundling folders into a docker image but have composer files excluded. Easy enough to re-include. I get it's important in a lot of deployment strategies, just didn't appreciate it necessarily for site operation. Cheers!
Interesting. I have a pretty basic site, so I'm not surprised I haven't needed in prod before.
Once I put composer.json in place with the extra.resource-dir config into production, all my URIs were corrected to '_resource' - I didn't realise SS relied on composer.json for operational config?
So the question I got is - should we be carrying around composer.json into production or is this just an interim thing?
Evening people. I jumped straight onto the '_resource' folder bandwagon and have been stumped for about an hour two as to how my dev and test containers were different: In dev, resource URIs were indeed being outputted with '_resource', but come test I was hitting all these 404s on theme resources. My test environment was outputting URIs with good ol' 'resources' directory. I couldn't see the differences between enviornments untill I diffed the crap outta the two. Then I realise, the only place I've configured the directory is in the composer.json - I strip those files out.