gitolite

gitolite or gitosis: permission on directory inside of the repository

ぐ巨炮叔叔 提交于 2019-12-29 07:17:11
问题 For example: I have a repository - repo1 with such fs hierarchy repo1: js html php/core php/menu And I want to give to repo1:php/menu , RW permission - to a freelancer, but for all repo1 - this freelancer must have only Read-Only permission. Can I do this with gitolite or gitosis or may be something else? 回答1: The repo access rights on a DVCS is always linked to the all repo, not part of if, mainly because you clone all of it (shallow clone is hard). That means gitolite (I won't even mention

git gitolite (v3) pre-receive hook for all commit messages

倖福魔咒の 提交于 2019-12-29 05:38:40
问题 I am trying to enforce a policy where each push gets rejected when even one of the commit messages does not satisfy a rule. I've distributed a hook to the devs in order for them to use it in their local repos but I also want to enforce this when they push to the origin. I have two questions: Should I use the update hook or the pre-receive hook? (I've tried to setup an update.secondary hook but it seems to me it doesn't get fired, while a pre-receive does). How can I get the message for each

Gitolite Update Hook exclude a repository

試著忘記壹切 提交于 2019-12-28 06:50:30
问题 I'm adding a gitolite update hook as a VREF and was wondering if there was a way to apply it to all of the repositories except for the gitolite-admin one. Having a simpler way rather than listing all of the repositories I want to apply the hook on would be great. Currently I have: repo @all - VREF/update = @all I was thinking of adding an exception above that one for the gitolite-admin repository. Something like: repo gitolite-admin RW+ VREF/update = @all repo @all - VREF/update = @all Is

Deploying Node Apps via Gitolite and post-receive hook

流过昼夜 提交于 2019-12-24 18:50:02
问题 I'm trying to get a fairly simple deploy process going for a Node app using Gitolite. I have Gitolite setup and working on my server, and I'm able to push to it fine. Gitolite is running under a user called git , and I've setup a node user that I'm hoping to use to run the Node app. My plan is to push the Node app to Gitolite, and then use a post-receive hook script to move the app files to the directory where the app lives, in this case /var/local/node-apps/my-node-app/ . I created the Node

GIT Server install failing on Ubuntu

流过昼夜 提交于 2019-12-24 18:15:12
问题 I'm trying to install my own git server with these instructions. http://cisight.com/how-to-setup-git-server-using-gitolite-in-ubuntu-11-10-oneiric/ But I am get stuck at this point. git clone --verbose gitolite@ec2-xxx.compute-1.amazonaws.com:testing.git Cloning into 'testing'... Permission denied (publickey). fatal: The remote end hung up unexpectedly And I think it has something to do with this: gitolite@ip-xxxx:~$ gl-setup tmp/john.pub key_read: uudecode

Gitolite 3 - Setting repo description (not authorized)

徘徊边缘 提交于 2019-12-23 15:52:19
问题 I'm using Gitolite 3.6 $ ssh git@host info hello you, this is got@Git running gitolite3 v3.6.1-6-gdc8b590 on git 1.7.10.4 [...] R W my_project [...] Following the documentation on setting the repo description $ ssh git@host desc my_project "Machin chouette" FATAL: you are not authorized How can this be explained ? git@host $ cat ~/.gitolite.rc [...] ENABLE => [ [...] 'desc', 'cgit', ] [...] 回答1: I found what was missing by reading the code of the desc command (didn't see it in the doc) git

Gitweb failure: fatal: missing object 0000000000000000000000000000000000000000 for refs/heads/master [closed]

梦想与她 提交于 2019-12-23 10:51:54
问题 It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 8 years ago . I'm trying to use gitweb with a set of repositories that are managed with gitolite. We can successfully clone/push/pull from them over ssh with no problems. When I try to view the index page, I get the following

Gitolite hooks do not execute

為{幸葍}努か 提交于 2019-12-23 04:15:16
问题 I'm attempting to create a script to chmod the repo files to a new group after a push occurs. To test hooks, I created a hook that creates a file in /tmp/ just to check that the hook is working. It is not however. What I've done so far: First I created a script (~/.gitolite/hooks/common/update.secondary), then ran gl-setup [pubkey]. After numerous tries doing this, I checked the main hooks directory (/var/gitolite/hook/common/) and the script was not there. After that I put the script

gitolite - smart-http - gives uninitialised value for rc(“UMASK”)

随声附和 提交于 2019-12-23 03:08:46
问题 I'm getting the following error in my /var/log/apache2/error.log when I try to do a git clone to my server running gitolite with smart-http enabled [Wed Jul 25 21:53:36 2012] [error] [client 124.149.104.106] FATAL: warn\tUse of uninitialized value $rc{"UMASK"} in umask at /opt/git/gitolite-source/src/ gitolite-shell line 95, <DATA> line 1.<<newline>> I do have the UMASK value set to 0027 in /home/git/.gitolite.rc Any thoughts why the value isn't setting when called from an su_exec from a file

With a git hook, how do I force or check user identity?

拟墨画扇 提交于 2019-12-23 02:47:13
问题 I'm trying to setup a gitolite server. One problem that I find annoying in git is the username is not checked when committing code. This can lead to a possible "identity phishing" where user1 can commit some bogus code and set user2 as username. Then we'll blame user2. I'm looking for a way to check or force the username to be consistent with the committer's identity. 回答1: You can sign your commits using: git commit -S (only available since git 1.7.9) You can then use a server-side git hook