Thanks for the help. Really appreciated! I have good idea now how to do it.
Pretty cool that you whipped up the pastie code so quick. Nice work. Do you know Ruby also? Todd On Sep 15, 2:54 pm, Marek Wywiał <[email protected]> wrote: > On 15 Wrz, 17:24, sbtodd <[email protected]> wrote: > > > > > Your English is fine .... thanks a lot for the help > > > How do I go about creating an integrated image for an app with your > > approach: > > > * base code baseapp.git > > * seprated config and design files. deploy-somecompany.git, deploy- > > othercompany.git > > > My applications directory structure is like somewhat this: > > > *** Means it is different for each deployment > > > /config *** > > Capfile *** > > /db > > /lib > > /log > > /public/images > > /public/stylesheets > > /pubic/javascripts > > /public/site-design *** > > /test > > /tmp > > /vendor > > /views > > you can create somedeploy.git with directories: > /config *** > /Capfile *** > /public/site-design *** > > and create Makefile or somthing like that which ask for base app path > and then will make symlinks this directories to base app > > which that layout You can on deployment/development machine do: > * git clone g...@mygit:baseapp.git > * git clone g...@mygit:somedeploy.git > * cd baseapp; make deploy > * makefile should ask You for deploy path: absolute or relative, for > example: ../somedeploy > * makefile should do : ln -s ../somedeploy/config .; ln -s ../ > somedeploy/Capfile .; mkdir -p ./public; ln -s ../public/site-design ./ > public/; > > You can use make, ant, rake, phing - whatever You know - even simple > bash/python script > *http://pastebin.com/m54051d66 > > > > > How do I create a deploy-company.git and then populate the company > > specific deployment with the config files > > from this respository? > > > Thanks, Todd > > > On Sep 14, 11:16 pm, Marek Wywiał <[email protected]> wrote: > > > > On 15 Wrz, 05:09, sbtodd <[email protected]> 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 [email protected]: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- > > > othercompany.git > > > > 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/git-users?hl=en -~----------~----~----~----~------~----~------~--~---
