When not specified, Git will use permissions reported by umask This allows users belonging to the same group to push into that repository. Specify that the Git repository is to be shared among several users.
-shared: =(false|true|umask|group|all|world|everybody|0xxx).If GIT_DIR environment is not set or a directory is not specified, it is set to the current working directory. Developers do not work and edit files in this repository as it has no working area. A bare repository has no working files and is a repository only. Set the repository "description": edit file /srv/git/projectx.git/description.Note that this requires all developers to have a login shell account on the system.įor more on group access see managing Linux groups All programmers must be part of this group "dev" in order to have access to the repository. chgrp -R dev /srv/git/projectx.git/ chmod ug+rw -R /srv/git/projectx.git/ Change ownership of all files to the software developers group.cp hooks/post-update.sample hooks/post-update.git init -bare -shared=group /srv/git/projectx.git/.Generate the repository and allow the the user remote shell access to the git repository: Perl-GSSAPI.x86_64, perl-Net-SMTP-SSL.noarch or perl-TermReadKey.x86_64). See the EPEL or PBone RPM repositories for dependencies (eg perl-Authen-SASL.noarch, GUI tools: "git gui", git citool (alternative to commit) and man pages Web front-end: /var//etc/httpd/conf.d/git.conf git2u-gitweb - Simple web interface to git repositories.git2u-gitk - Git revision tree visualizer.
0 kommentar(er)
