{"thread":{"id":"21639","subject":"git multisite setup","startedAt":"2009-11-16T18:18:36Z","lastAt":"2009-11-17T00:50:40Z","messageCount":4,"participants":["Matt Di Pasquale","Nicolas Sebrecht"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"127694","messageId":"13f0168a0911161018r6fc67d29n781cca670a66815b@mail.gmail.com","threadId":"21639","inReplyTo":null,"subject":"git multisite setup","fromName":"Matt Di Pasquale","fromEmail":"liveloveprosper@gmail.com","sentAt":"2009-11-16T18:18:36Z","receivedAt":"2009-11-16T18:18:36Z","isPatch":false,"sender":{"key":"liveloveprosper@gmail.com","avatar":"https://gravatar.com/avatar/0c4196519680e2a9fd1d36ed00f95e0890a42d33652623fe1c305be1ea0d6f0a?d=mp&s=160"},"body":"Hi,\nIn my sites folder i have folders for different sites of mine:\nexample.com example2.com, and i also have generic files like an\nincludes dir and a .htaccess file that all sites use. what is the best\nway to track the generic files and the different sites?\n\ni was thinking each site has its own .git repo. and then make a .git\nrepo for my sites folder but ignore the individual sites dirs.\nactually that's what i'm doing now.\n\nshould i use submodules? i don't really understand submodules and the\nexamples i saw did not cover nested folders\n\nThanks!\n\nmatt\n"},{"id":"127716","messageId":"20091117001320.GA13074@vidovic","threadId":"21639","inReplyTo":"13f0168a0911161018r6fc67d29n781cca670a66815b@mail.gmail.com","subject":"Re: git multisite setup","fromName":"Nicolas Sebrecht","fromEmail":"nicolas.s.dev@gmx.fr","sentAt":"2009-11-17T00:13:20Z","receivedAt":"2009-11-17T00:13:20Z","isPatch":false,"sender":{"key":"nicolas.s.dev@gmx.fr","avatar":null},"body":"The 16/11/09, Matt Di Pasquale wrote:\n\n> In my sites folder i have folders for different sites of mine:\n> example.com example2.com, and i also have generic files like an\n> includes dir and a .htaccess file that all sites use. what is the best\n> way to track the generic files and the different sites?\n> \n> i was thinking each site has its own .git repo. and then make a .git\n> repo for my sites folder but ignore the individual sites dirs.\n> actually that's what i'm doing now.\n\nThis looks good to me. Why would you like to change?\n\n-- \nNicolas Sebrecht\n"},{"id":"127718","messageId":"13f0168a0911161617o56757488n45328714fb1d3bea@mail.gmail.com","threadId":"21639","inReplyTo":"20091117001320.GA13074@vidovic","subject":"Re: git multisite setup","fromName":"Matt Di Pasquale","fromEmail":"liveloveprosper@gmail.com","sentAt":"2009-11-17T00:17:03Z","receivedAt":"2009-11-17T00:17:03Z","isPatch":false,"sender":{"key":"liveloveprosper@gmail.com","avatar":"https://gravatar.com/avatar/0c4196519680e2a9fd1d36ed00f95e0890a42d33652623fe1c305be1ea0d6f0a?d=mp&s=160"},"body":"yeah. i guess it's fine. :) just that the specific git repos aren't\ncoordinated to the generic one. but that's fine so far since i haven't\nhad to jump around to different commits and the generic has stayed\npretty much the same.\n\nOn Mon, Nov 16, 2009 at 7:13 PM, Nicolas Sebrecht <nicolas.s.dev@gmx.fr> wrote:\n> The 16/11/09, Matt Di Pasquale wrote:\n>\n>> In my sites folder i have folders for different sites of mine:\n>> example.com example2.com, and i also have generic files like an\n>> includes dir and a .htaccess file that all sites use. what is the best\n>> way to track the generic files and the different sites?\n>>\n>> i was thinking each site has its own .git repo. and then make a .git\n>> repo for my sites folder but ignore the individual sites dirs.\n>> actually that's what i'm doing now.\n>\n> This looks good to me. Why would you like to change?\n>\n> --\n> Nicolas Sebrecht\n>\n"},{"id":"127720","messageId":"20091117005005.GC13074@vidovic","threadId":"21639","inReplyTo":"13f0168a0911161617o56757488n45328714fb1d3bea@mail.gmail.com","subject":"Re: git multisite setup","fromName":"Nicolas Sebrecht","fromEmail":"nicolas.s.dev@gmx.fr","sentAt":"2009-11-17T00:50:40Z","receivedAt":"2009-11-17T00:50:40Z","isPatch":false,"sender":{"key":"nicolas.s.dev@gmx.fr","avatar":null},"body":"[ Please, don't top-post nor whole quote. ]\n\nThe 16/11/09, Matt Di Pasquale wrote:\n\n>                                       the specific git repos aren't\n> coordinated to the generic one. but that's fine so far since i haven't\n> had to jump around to different commits and the generic has stayed\n> pretty much the same.\n\nI'm not sure to understand exactly what kind of coordination you expect\nexactly (because you don't describe what you'd like that much), but\nsubmodule could be what you need, yes.\n\nFMHO, the best way to check if you need it is to try it. For a good\nstart, I guess you'll need to change your approach on \"what depends of\nwhat\". I think you should consider the _common_ part to be the\n_dependency_; as a consequence, it should be the submodule used in the\nother repositories. AFAIR, submodule was originaly designed to make our\nlife easier with libraries. It may fit to your needs too but again, the\nbest thing to do is to try.\n\n-- \nNicolas Sebrecht\n"}]}