gitosis

Why I can't add new repositories using gitosis?

点点圈 提交于 2019-12-21 02:38:29
问题 I set up gitosis but even when i can clone, pull and push to the gitosis-admin repo, i can't create new ones. According to every doc i read, to create a new repo one has to: Give user write access to the repo (inside a group put: writable = repo-name) The user create a repo locally add a remote then does a push The repo is created in the server But i always get the error fatal: 'repo-name.git' does not appear to be a git repository But if a login on the server (as user git) and create the

Git keeps asking for password

假如想象 提交于 2019-12-19 19:02:30
问题 I've searched and searched, for what seems like hours, for a solution to this problem and nothing I've tried works. Let me preface all this by saying that while I've used *nix before, I'm pretty much a noob so I'm sure I missed a step in the setup of Git somewhere. I set up a Ubuntu box on the network at work to host our new Git repo. The box is running Git, Gitosis, and also ViewGit. Everything seems to be set up correctly, and I can view the repo I've added inside of ViewGit. The problem is

Using gitosis to specify permissions per branch?

落爺英雄遲暮 提交于 2019-12-18 20:02:10
问题 With gitosis, is it possible to specify write permissions so that users can push freely to branches with their own name, but not merge with the master? E.g. $USER/test1 .. $USER/test5 This mean you could host just one repository per project, rather than hosting multiple repositories for the same project, specific to each user: project1-user1 project1-user2 project1-user3 ... project5-user1 project5-user2 project5-user3 回答1: Gitosis controls access to repositories, but not by branch or commit.

Why do you need Gitosis or Gitolite?

亡梦爱人 提交于 2019-12-17 21:12:17
问题 Sorry for my ignorance - but what is the gain of having either Gitosis or Gitolite. I have a Synology NAS server running, but could I not just create a "bare" on any folder on the NAS? Regards 回答1: See my answer about "authentication and authorization": a DVCS (Distributed VCS) has none. Gitosis is dead (obsolete, not maintained). Gitolite is about authorization, not authentication. You will couple that authorization mechanism with authentication ones, using ssh or httpd. However, it has to

Problem with Hudson + Git + Gitosis on windows

独自空忆成欢 提交于 2019-12-17 20:59:01
问题 I have git and gitosis running smoothly on windows with msysgit (with OpenSSH), and I would now like Hudson to start using git. So, I have ensured that the hudson windows service is running as the hudson user, and I have added the hudson user through gitosis-admin. I also have unixutils, and they are in the windows path. But, Hudson fails at clone the project. I can clone my project using git bash, when logged in as the hudson user, but not on the windows command line, and I am afraid this is

Gitosis post-receive hook to deploy repository getting public key errors

混江龙づ霸主 提交于 2019-12-17 14:56:30
问题 I have gitosis setup on my server and I'm trying to create a post-receive hook that will checkout changes to a working directory on the remote machine. Initially I got an error saying cannot open /home/user/source/testing-local/.git/FETCH_HEAD: Permission denied so I changed the group ownership of the working directory's .git folder to the git user. Following this I got the error Host key verification failed which led me to check which user was running the hook, git of course (silly me!), so

Gitosis won't create repository

点点圈 提交于 2019-12-13 09:36:05
问题 I'm testing my new Git repository. I converted from Subversion to Git, no problem. Now, on my laptop git remote add origin git@server:test.git returns correctly. But when I do git push I get error:gitosis.serve.main:repository read access denied And when I go to /srv/git/repositories on the server, the new repository isn't created. Is there a log file that I can look at somewhere to figure out what's going on? 回答1: Carefully follow the "Setting Up" portion of the README. It describes access

Git post-receive hook not working

拥有回忆 提交于 2019-12-12 08:22:59
问题 We're using git with a central repo (using Gitosis). I've created a post-receive hook to generate an email to the dev mailing list whenever changes are pushed to the central repo, and to generate documentation from the documentation folder in the git repo. Therefore, in ~git/ I've got a directory, we'll call it 'a' that contains a clone of the git repo. The post-receive hook looks like: #!/bin/bash cd ~git/repositories/a.git . ~git/post-receive-email &> /dev/null ( cd ~git/a && git pull &>

How do I recover from pushing a gitosis.conf file with parsing errors due to line breaks?

天大地大妈咪最大 提交于 2019-12-12 08:22:33
问题 I have successfully set up gitosis for an Android mirror (containing multiple git repositories). While adding a new .git path following writable= in gitosis.conf I managed to insert a few line breaks. Saved, committed and pushed to server when I received the following parsing error: Traceback (most recent call last): File "/usr/bin/gitosis-run-hook", line 8, in load_entry_point('gitosis==0.2', 'console_scripts', 'gitosis-run-hook')() File "/usr/lib/python2.5/site-packages/gitosis-0.2-py2.5

Git aliases that are stored in origin

不羁的心 提交于 2019-12-12 07:36:24
问题 I use git with a big development team and I'd like to have a set of aliases be common across every developer. They change every so often, so I'd like to store them in origin somehow. Is there any way to set that up in git? I'm using gitosis for the git server (not sure if that would make a difference). 回答1: 1) Create .gitalias files with something like this: [alias] # full status s = !git status -sb && git submodule foreach --recursive git status -sb 2) Commit this file. 3) Add following