#Needs documentation

Re #5: Yeah, I'm not necessarily saying it's a workflow that anyone would actually use, but I merely raise it because people have all sorts of wonky workflows and this could be a major change to some of them. I guess this is merely a call for strong documentation.

This is probably the riskier proposition, since deployments that depend on doing a composer install at the remote end, then reapplying the recipes, will not work

Trying to think of a use-case for this workflow, but struggling a bit.

I would expect that people would apply the recipes locally, export configuration, and commit the configuration to git, then import it on production (same as config changes without recipes). Or.. if they're building a recipe-based hosted demo or similar that they'd commit the recipes themselves to git. As long as those two work, then breaking a workflow of composer install locally + recipe apply remote without either exporting config or committing to git seems fine.

Thanks for opening that!