Re: [git-users] What is the best way to use GIT for versioning Java Website
From: gaug...@gmail.com 1) Each developer having his own contetnts in a separate directory is not able to test the code before pushing it to the bare repo which would update the Work Directory- Coz of these steps even for say one jsp file change I end up doing 20 commits until it starts working properly without bugs since we have tomcat pointing to only the original work directory. It seems to me that the problem isn't the Git workflow itself, but that you have no way of testing a Dev version of the Website without installing the change into the live Website. (Or perhaps I am misunderstanding your situation.) Since you clearly don't want to install the change into the live Website before you have tested it, you need some sort of testing facility. Dale -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[git-users] What is the best way to use GIT for versioning Java Website
I have a git repo installed in my unix for version tracking our JEE website. I have currently run into issues not in the usage of git but the way in which I am suppose to use it which is explained below. I work in a team of 3 developers which contribute to the website development. Initially when I installed Git in our server I directly created a repo of our webapps directory which contains the actual work files and ran into the foll problems. 1)While committing the changes into the repo one of us would genrally do a git add . and commit it to the repository which would commit not only the files the commiter changed but would also commit the changes of other developers. When we faced this issue we decided that we needed to create separate non-bare repos for each one of us in the same server in different directories which would house the entire code.The basic work stucture we are following is hown below: https://lh4.googleusercontent.com/-qKXGpVl_8Uc/UQTiLE0LvgI/AAY/Q-H-TU0WtKA/s1600/git_arch.png As shown above in the image we have created a bare repo which would have the website contents pushed by the webapps which in the image is the Work Directory. The basic workflow here is: 1) Create n number of non-bare repos for each and every developer. 2) Get the entire website work files from pulling from that bare repo 3) After making changes to our own repo push to the bare repo 4) The bare repo being configured with a post-receive hook would actually update the Work Directory. This setup is working fine but we are facing a lot of issues as shown below: 1) Each developer having his own contetnts in a separate directory is not able to test the code before pushing it to the bare repo which would update the Work Directory- Coz of these steps even for say one jsp file change I end up doing 20 commits until it starts working properly without bugs since we have tomcat pointing to only the original work directory. This has become the most troubleseme issue here. How can we improve this scenario where using GIT in out prject seems benefitial. Can anyone suggest any ways for improving the same. --
