I'm not a webmaster of any sort. My personal opinion, as a git newbie, is that I would likely have a separate git branch for each distributor in the same repository.The main reason, for me, for this instead of separate repositories is because so much is shared. With separate repositories, you'd have "n" copies of every module, most of which are supposed to be identical. So, the "master" branch would contain the shared files, along with a "template" version of the unique files (if the unique files are identically named). Each distributor branch would contain the modified and unique files for that distributor.
I'm not any kind of expert, but this seems easiest to me. On Tuesday, November 13, 2012 5:38:41 AM UTC-6, Ugo wrote: > > Hello, > > I'm currently running multiple websites on Magento for a worldwide > company. At first it was only an US version and then an EU version, but now > we're going to open one website per distributor. > Basically, there could be 8 or 10 Magento websites running in the long run. > > The thing is that each distributor wants to change a few little details. > Basically the core is the same, but there could be one extra module (a > payment provider), or a few line of codes different from one website to > another. > > I need to manage this correctly, because it won't work otherwise and take > too much time. > > Do you have idea on what's the best use with GIT for my case ? > Should I do a fork on the main master ? create a branch for each > distributor ? > > How can I manage update from the master, and spread them to each > distributor website ? > i.e : updating the core of Magento (lots of files). > > Any idea/tips would be greatly appreciated. > > Thanks a lot, > > Ugo > --
