Consider if some functionality of the template can be turned into packages
mallorydxw opened this issue · comments
F:
We talked about the right solution for that need was probably packaging functionality up and relying on dependency versioning instead.
What would this look like? Perhaps script/update runs composer update and one of the composer dependencies has a post-install task that replaces docker-compose.yml?
I feel like this makes sense, particularly given #3. Using packages would give us an easy way of managing breaking changes and the like.
I still think we should do this. But this can be a gradual thing that we do as the template evolves. It shouldn't be something that blocks us from making a start on the template.