Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am trying to implement Git in my office. As it is not possible to run apache server on each developer machine, they can’t work with clone on their machine. We have a development server with NFS share. I am planing to create git repository and working tree on this NFS share. Git is managed by single user so there will not be any simultaneous push.
My questions are
Restating here to make sure I am understanding: a shared development “working area”, which everyone mounts over NFS and develops on using their browser pointed at the remote apache instance, they work on the same set of files and execute git commands against the same git working copy. If I’m correct in my understanding so far, that does not sound like a good idea.
I would recommend you give each developer their own working area on the apache server, and also their own VirtualHost so they can see their independent files. Now they are able to work independently from other developers. Each of those sets of files would be a git clone of the same repository (probably a bare repository somewhere). This allows for a much saner development workflow for each developer, and there is no risk of developers trampling each other and committing other’s code, etc.
User access, you can control this via who is allowed to mount the NFS share.