Symphony.

Hello people, been setting up a fork of Symphony for use in my own projects and wanted to include a few submodules of my own before pulling the fork into any local dev environments..

Now I manually added a few I know I wanted into the github fork and commented that manual change.

But... whenever I try to clone the repo It only pulls the submodules already included with the master symphony repo and deosn't grab my added modules... any chance a hint as to where things are going wrong/not quite setup right?

I'm guessing it's to do with the manual editing of the .gitmodules file but... not sure how else to ensure the submodules I want are included when I pull from my fork in the future.

Now I manually added a few I know I wanted into the github fork and commented that manual change.

I don't understand that, moonoo2 - could you elaborate?

In your fork:

symphony_root_dir$ git submodule add git://github.com/user/extension.git extensions/extension_name

Then a git status should show the addition of the submodule, with the files/directory already staged. Do a commit:

symphony_dir$ git commit -m 'Adding an extension'

Then, when you've pulled in the commit to another machine/installation, it should pull down your extra submodules:

symphony_dir$ git submodule update --init --recursive

Related, after cloning Symphony for a new project, I create a branch just for that project which contains any project-specific submodules.

Thanks David, I think I'm adding the additional submodules into the git repo origin stored at github. But there is no reference in the config file /.git/config online as to the additional submodules when I try to update them.

I'm basically doing it ass backwards and not pulling/adding the submodules the traditional way and instead trying to setup the repo to recognise that these additional submodules exist/seen by git from the online repo... i.e trying to think of a way that avoids the manual pull of individual modules/extensions each time I setup a new base repo for my symphony builds.

Hope that makes half sense.. cos when I re-read it, it makes less sense to me.. tricky one to write down I guess.

Do you want the extensions to exist as submodules in your new projects? (That's how I do it, but I'm not sure from your posts if this is what you want.)

Once you've done a git submodule add and committed the result, all you have to do is a git submodule update --init --recursive and Git will automatically pull in all the extensions you've added.

Yes exactly that.. I do this method regularily but I was thinking if there was a way of setting it up before any local repos exist.