5 ms·
>It makes absolutely sense to have a repository for the gui and one for the server. Not really. You can have a single repo with top level directories tigershar
by fnord123 8y ago
>It makes absolutely sense to have a repository for the gui and one for the server.
Not really. You can have a single repo with top level directories tigershark-gui and tigershark-server.
- tigershark 8y agoWhat is the point instead of having them in two separate repos?
- lkschubert8 8y agoAny full stack change will be represented by one PR that changes from pre change to post change. Two repos would introduce a new possible state where one has the change applied and the other doesn't.
- rimliu 8y agoAnd later you add the iOS and Android clients too. Will those go into the same repo? Better to keep server and clients apart, especially if release schedules are different.
- fnord123 8y agoSure if the release schedules are different then have them in separate repos so things like tagging makes sense. But often people work with a single release schedule. There's just so many variables that go into these decisions that the thread here is bonkers. Smart people can work through problems to get the job done. Monorepo vs polyrepo won't stop people from moving forward.