I like this answer, for I see Discourse’s devs on par with Google themselves.
Understanding AMP’s mechanisms of action, their parts, how they work together, flow then becomes a blueprint for Discourse; by adding these little JavaScript parables and lessons to their own Ember.js foundation.
Sam, you already do this behavior elsewhere and for the same reason as I stated above. You did it by creating launcher in lieu of using Docker Compose.
This be only a suggestion–one that, if taken, can be tackled over time (as you all do well already in other areas) and improve Discourse’s perf: the reason. *smile*