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.
We are working on a project composed of about a dozen different modules. Each module is a small application per se (some of them are Rails apps, some are daemon services, etc.)
We are hesitating between 2 options:
1/ One git repo with one folder per module
2/ Several git repos (one per module)
Which approach is the best ?
One repo per module is usually best, especially if they can evolve and being tagged independently one from another.
This is akin to a component-based approach, and similar to what I proposed in “Component based web project directory layout with git and symlinks“.
But if you cannot make any change in one without having to modify another component (or several others), then and only then, one repo would make sense.
That would be called the “system approach” in a “Component-driven development”.
The other argument for one repo would be if all those components have only a few files in them (and not tens or hundreds of files).