gitolite

Regenerate authorized_keys file in gitolite?

我的梦境 提交于 2019-12-01 09:23:56
Is it possible? My authorized_keys file was wiped, updating gitolite admin rules only appends to file. Is it possible to regenerate the whole file based on gitolite config? EDIT: found it! gitolite trigger POST_COMPILE With gitolite g3 (the version 3.x), a simple: gitolite setup (executed on the server) is enough. See src/lib/Gitolite/Setup.pm : Setup gitolite, compile conf, run the POST_COMPILE trigger (see rc file) and propagate hooks. This one command is easier to remember than gitolite trigger POST_COMPILE . 来源: https://stackoverflow.com/questions/16004729/regenerate-authorized-keys-file

Gitolite error .gitolite.rc' seems to be for older gitolite; please see doc/g2migr.mkd

可紊 提交于 2019-12-01 09:08:07
问题 I have installed gitolite using rpm in centos6 ie gitolite-2.3.1-1.el6.noarch.rpm and after rpm installation I have run the gl-setup . I am trying to access repo over http. When I try to clone git clone http://server.name/git/gitoliteadmin.git it gives error: FATAL: '/var/opt/jet/gitolite/.gitolite.rc' seems to be for older gitolite; please see doc/g2migr.mkd (online at http://gitolite.com/gitolite/g2migr.html) Premature end of script headers: gitolite-shell Below is my htpd.conf

git change default branch (gitolite)

橙三吉。 提交于 2019-12-01 08:40:50
I've got a repository with branches: master and devel. Master is the default one. I want to rename master into prod and make it default (and push it to the server). How to do this? Repository is hosted in gitolite (if it matters). VonC You need to have access to the server in order to change the symbolic-ref of HEAD to the branch you have pushed there ( prod ). git-symbolic-ref HEAD refs/head/prod I tentatively proposed a way to do that from a client at the end of " How do I change a Git remote HEAD to point to something besides “master” ", but it is easier if you can log on the server

ssh config is working from home, but not working from another directory

∥☆過路亽.° 提交于 2019-12-01 08:05:34
问题 I could solve my problem, but I'm pretty curious why it isn't working the way it should be. The problem: In ~/.ssh/config there is an entry: Host git HostName git.myserver.com User gitolite Identityfile gitolite After that in my home directory when I run: ssh git it returns this text (which is a normal thing): PTY allocation request failed on channel 0 hello myname, this is gitolite@myserver.com running gitolite3 v3.4-3-g797a81f on git 1.7.2.5 R W myrepo1 R W myrepo2 R W . R W . R W .

How to solve 'invalid repo name' Git error?

此生再无相见时 提交于 2019-12-01 06:14:57
问题 I've installed Gitolite, just like said in GitLab instructions, til now it was all ok, repo's created... but when tried to clone or push, it returns NO repo found - or something similar. But when I set my remote to the full path like git@server:22/~git/repositories/repo.git it clones, but when try to push, its caught an error: git push origin master ERROR: invalid repo name. fatal: The remote end hung up unexpectedly What can it be? 回答1: That error message comes from "gitolite-shell.parse_soc

Regenerate authorized_keys file in gitolite?

微笑、不失礼 提交于 2019-12-01 05:48:59
问题 Is it possible? My authorized_keys file was wiped, updating gitolite admin rules only appends to file. Is it possible to regenerate the whole file based on gitolite config? EDIT: found it! gitolite trigger POST_COMPILE 回答1: With gitolite g3 (the version 3.x), a simple: gitolite setup (executed on the server) is enough. See src/lib/Gitolite/Setup.pm: Setup gitolite, compile conf, run the POST_COMPILE trigger (see rc file) and propagate hooks. This one command is easier to remember than

gitolite setup getting FATAL: fingerprinting failed for '/tmp/Q3pnE4WVbu'

依然范特西╮ 提交于 2019-12-01 04:32:46
I am installing gitolite on a CentOS 5.9 server. I have created the git user, then after su - git I have managed to get my public key into the ~/.ssh/ directory, I have successfully cloned the gitolite repo from github and have run gitolite/install -ln . Next step is to run gitolite setup. git@hostname [~]# gitolite setup -pk $HOME/.ssh/micha.pub Initialized empty Git repository in /home/git/repositories/gitolite-admin.git/ Initialized empty Git repository in /home/git/repositories/testing.git/ FATAL: fingerprinting failed for '/tmp/Q3pnE4WVbu' Google search and a search here on SO have not

搭建git服务器配置gitolite[迁移原来的gitolite工程]

一个人想着一个人 提交于 2019-12-01 02:22:16
参考 https://www.liaoxuefeng.com/wiki/896043488029600/899998870925664 http://www.worldhello.net/gotgit/05-git-server/040-gitolite.html 1. 安装git sudo apt-get install git 2. 创建git用户 sudo adduser git 目的是为了方便管理 3. 创建自己client公钥 把公钥拷贝到服务器,然后在 /home/git/.ssh/authorized_keys配置好。 4. 初始化git仓库 切换到git用户,然后初始化一个git仓库 sudo git init --bare sample.git 这样初步的服务器就完成了,如果人数太多,觉着每次配置公钥太麻烦可以使用gitolite 5. 安装gitolite 在git用户下,在git的home目录 参考 https://github.com/sitaramc/gitolite git clone https://github.com/sitaramc/gitolite mkdir -p $HOME/bin gitolite/install -to $HOME/bin bin/gitolite setup -pk liangbenming.pub 这样就配置好了

issue in gitolite

Deadly 提交于 2019-12-01 02:01:10
I have installed the gitolite in the a machine which act as a git server. I have cloned that gitolite in my local machine. Configured some repositories and user rights. While making any changes in the gitolite.conf and pushing it, the changes are not taken into the gitolite.conf-compiled.pm file. Everytime I am manually correcting the changes in that file(gitolite.conf-compiled.pm). What is the issue here. Kindly clarify 来源: https://stackoverflow.com/questions/10207919/issue-in-gitolite

gitolite setup getting FATAL: fingerprinting failed for '/tmp/Q3pnE4WVbu'

匆匆过客 提交于 2019-12-01 01:14:20
问题 I am installing gitolite on a CentOS 5.9 server. I have created the git user, then after su - git I have managed to get my public key into the ~/.ssh/ directory, I have successfully cloned the gitolite repo from github and have run gitolite/install -ln . Next step is to run gitolite setup. git@hostname [~]# gitolite setup -pk $HOME/.ssh/micha.pub Initialized empty Git repository in /home/git/repositories/gitolite-admin.git/ Initialized empty Git repository in /home/git/repositories/testing