Open yaronkoren opened 1 year ago
Making it a mono repo makes some sense from developer's perspective, but this would also mean that users wanting to deploy Canasta via Compose or K8s will also have to clone all the image source files, and this can be not very convenient
We've talked about this before at various times, but a GitHub issue seems like the best place for a full discussion. So: this is to discuss the possibility of merging in the Canasta-DockerCompose and Canasta-Kubernetes repositories into the main Canasta repository (i.e., this one). On the surface, this seems like a reasonable idea: it would prevent the possibility of inconsistency between the different repositories, it would make life easier for developers (and maybe administrators too); and there actually isn't that much code in these other two repositories - and actually, for that matter, there isn't all that much code in this one. On the other hand, there may be valid reasons to keep all three repositories as they are now. Any thoughts on this are welcome.