Closed MetroCat69 closed 6 months ago
I believe we are going to use a mono repo for it, at least for now, to easily manage the source. We can split it into multiple repos if we find that the project becomes too difficult to handle as a mono repo.
I am saying maybe we should do one repo for front and one repo for back
Yeah, I understand. However, it seems much easier to wrap everything around Dockers and Docker-compose (maybe even k3s soon) -> test using GitLab CI/CD \ unitests (I am using it and mirroring to Github) -> and push for deployment on a server. Using two repositories for each service may create some difficulties in testing the front-end against the back-end if one or the other changes (in my opinion). Anyway, lets start and change the structure if needed.
@MetroCat69 Do you have discord?
should we do a mono repo? shouldnt we do multi repo here?