On 15 Wrz, 05:09, sbtodd <tdew...@gmail.com> wrote:
> I know enough Git basics to setup a local and remote repository
> $ git init
> $ git add .
> $ git commit -m "Added initial Rails app"
> $ git --bare init  ::Initialize empty Git remote repository at
> server.com
> $ git remote add origin usern...@server.com:git/app.git
> Push to Remote
> $ git push origin master
> Pull from Remote
> $ git pull origin master
> I am at the point now where I need to create multiple applications/
> websites from the same
> code base.
> The difference between the apps/sites is mostly config files and
> design files (images and templates)
> I want to be able to make changes in the base app and have the change
> go to the other apps.
> I also want to source control the config files and design files for
> each app/site.
> What is the best way to do this?  ... branches?

We are providing code similar way:
 * base code baseapp.git
 * seprated config and design files. deploy-somecompany.git, deploy-

path to installed baseapp are stored in config files

In other way You can use branches for applications, and branches for
features/bugs, and then You can use git merge, or git cherry-pick to
get features/bugs in all applications branches.

Sorry if my english is not so good.
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to