Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider if some functionality of the template can be turned into packages #4

Open
mallorydxw opened this issue Jul 24, 2020 · 2 comments

Comments

@mallorydxw
Copy link
Contributor

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?

@RobjS
Copy link
Contributor

RobjS commented Jul 27, 2020

I feel like this makes sense, particularly given #3. Using packages would give us an easy way of managing breaking changes and the like.

@mallorydxw
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants