Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
You are building a software with separated client and server-side code (different people) – would you create one repository or two?
E.g., we have front-end developers who are not working with server code, so they are not interested in checking it out. A server-side developer doesn’t change client-side code too, but he is responsible for building/deploying the whole application. What is best practice?
I would set it up as separate repositories and use submodules to import them into a big main repository that can be used to synchronize and test. Any shared code can be created in a library project (another repo). Might seem like an overkill for a smaller project but as the code base starts to grow it will prove quite useful.