温馨提示！由于新浪微博认证机制调整，您的新浪微博帐号绑定已过期，请重新绑定！&&|&&
LOFTER精选
网易考拉推荐
用微信&&“扫一扫”
将文章分享到朋友圈。
用易信&&“扫一扫”
将文章分享到朋友圈。
1. 管理员从用户那获取用户的公钥，并将公钥按照username.pub(只要能区分人员就好，邮箱.pub也可以)格式重命名。2. 管理员在本机版本库(gitolite-admin)中，复制新用户的公钥到 keydir/ 目录下3. 执行git add keydir 命令 将所有新增加的公钥添加到暂存区4. 执行git commit -m 'add some user' & 将暂存区的内容添加到本地库5. 执行git push 命令 将 本地库 推送到远程库(即gitolite服务器上的gitolite-admin中)授权：&管理员进入本地哭gitolite-admin中，编辑conf/gitolite.conf&& && & & &&&&&&
阅读(2903)|
用微信&&“扫一扫”
将文章分享到朋友圈。
用易信&&“扫一扫”
将文章分享到朋友圈。
历史上的今天
在LOFTER的更多文章
loftPermalink:'',
id:'fks_',
blogTitle:'gitolite 之添加新用户及授权',
blogAbstract:'添加新用户：1. 管理员从用户那获取用户的公钥，并将公钥按照username.pub(只要能区分人员就好，邮箱.pub也可以)格式重命名。2. 管理员在本机版本库(gitolite-admin)中，复制新用户的公钥到 keydir/ 目录下3. 执行git add keydir 命令 将所有新增加的公钥添加到暂存区4. 执行git commit -m \'add some user\' & 将暂存区的内容添加到本地库5. 执行git push 命令 将 本地库 推送到远程库(即gitolite服务器上的gitolite-admin中)',
blogTag:'gitolite,创建用户,授权',
blogUrl:'blog/static/',
isPublished:1,
istop:false,
modifyTime:9,
publishTime:2,
permalink:'blog/static/',
commentCount:0,
mainCommentCount:0,
recommendCount:0,
bsrk:-100,
publisherId:0,
recomBlogHome:false,
currentRecomBlog:false,
attachmentsFileIds:[],
groupInfo:{},
friendstatus:'none',
followstatus:'unFollow',
pubSucc:'',
visitorProvince:'',
visitorCity:'',
visitorNewUser:false,
postAddInfo:{},
mset:'000',
remindgoodnightblog:false,
isBlackVisitor:false,
isShowYodaoAd:false,
hostIntro:'',
hmcon:'1',
selfRecomBlogCount:'0',
lofter_single:''
{list a as x}
{if x.moveFrom=='wap'}
{elseif x.moveFrom=='iphone'}
{elseif x.moveFrom=='android'}
{elseif x.moveFrom=='mobile'}
${a.selfIntro|escape}{if great260}${suplement}{/if}
{list a as x}
推荐过这篇日志的人：
{list a as x}
{if !!b&&b.length>0}
他们还推荐了：
{list b as y}
转载记录：
{list d as x}
{list a as x}
{list a as x}
{list a as x}
{list a as x}
{if x_index>4}{break}{/if}
${fn2(x.publishTime,'yyyy-MM-dd HH:mm:ss')}
{list a as x}
{if !!(blogDetail.preBlogPermalink)}
{if !!(blogDetail.nextBlogPermalink)}
{list a as x}
{if defined('newslist')&&newslist.length>0}
{list newslist as x}
{if x_index>7}{break}{/if}
{list a as x}
{var first_option =}
{list x.voteDetailList as voteToOption}
{if voteToOption==1}
{if first_option==false},{/if}&&“${b[voteToOption_index]}”&&
{if (x.role!="-1") },“我是${c[x.role]}”&&{/if}
&&&&&&&&${fn1(x.voteTime)}
{if x.userName==''}{/if}
网易公司版权所有&&
{list x.l as y}
{if defined('wl')}
{list wl as x}{/list}博客分类：
部分内容参考自：
1.git基础配置
git config --lis
用户名和邮箱，如果已填写过则PASS
git config --global user.name "username"
git config --global user.email ""
2.生成SSH密钥(mysshkey是别名，可以任意)
ssh-keygen -t rsa -C "mysshkey"
第一个提示输入保存文件名，默认为空，回车。
第二个提示输入密钥，默认为空，回车
第三个确认刚输入密钥，默认为空，回车
完成后，默认保存位置当前
用户名下/.ssh/id_rsa 和id_rsa.pub（windows8和10下位置是：C:\Users\用户名）
3.设置密钥
在Gitblit管理后台创建新用户；
上面创建的git server的用户，这里创建的Gitblit内部用于管理权限的用户，两者要同名，当通过https链接git服务器时，需要输入用户名和密码，密码就是GitBlit中创建用户时填写的密码。
创建好以后，用新账号登陆（不是admin账号），然后在当前用户的用户中心把 id_rsa.pub 中的内容复制到
SSH Keys，保存确定。下图中我已经添加好一个SSH Key了：
4.clone 克隆设置
ssh://test@192.168.0.254:29418/test.git
注意：ssh请求才能无密码访问，ssh key对https请求无效。
Gitblit Git 无密码clone 设置完成。
遇到的问题：
以上设置完毕后能保证git bash命令行下无需输入密码clone、push、pull等操作，但是在TortoiseGit中进行操作还是要输入密码，此时还需要在TortoiseGit中设置一下SSH client，修改为Git目录下的ssh.exe，例如：D:\Program_Files\Git\usr\bin\ssh.exe：
浏览: 697947 次
来自: 宜昌
请问博主试过这个方法吗？有效吗？
molixiaogemao 写道shipping模式下同步默认 ...
shipping模式下同步默认可以开启,具体参考 GitHub ...
jacksparow 写道博主你知道，在UE4里有那些方法可以 ...
博主你知道，在UE4里有那些方法可以获取其他对象的变量？用c+ ...
(window.slotbydup=window.slotbydup || []).push({
id: '4773203',
container: s,
size: '200,200',
display: 'inlay-fix'博客访问： 270743
博文数量： 38
博客积分： 455
博客等级： 下士
技术积分： 435
注册时间：
IT168企业级官微
微信号：IT168qiye
系统架构师大会
微信号：SACC2013
分类： 项目管理
首先到官网下载最新版本的Gitblit GO&
解压缩到本地目录中&E:\git\gitblit132
官方文档：
一、 服务器配置
打开配置文件&data/gitblit.properties&
server.httpPort = 7070&
server.httpsPort = 0
&注意：&server.httpBindInterface = localhost &修改成&server.httpBindInterface =
& & & & & &把localhost删除，否则，局域网能其他电脑没法通过http://ip-address:7070 访问
运行&gitblit.cmd ，启动服务
& & & & &可以通过运行installService/uninstallService把服务器安装到windows系统服务中，且自动启动
& & & & &不过需要注意的是，在运行这两个bat文件之前，需要修改其中的set ARCH=x86这一行修改为自己操作系统对应的位数
& & & & &安装完之后的服务名叫做gitblit，以后就可以通过gitblitw来管理了，像tomcat，apache一样
访问&http://localhost:7070/
用admin/admin登录，居然是中文版界面，很好很强大！
在用户管理界面，可以把admin的密码修改掉
新建用户blankerer/123456&
接下来新建一个仓库，名称叫做 ci
所有者授权给用户blankerer
授权控制选择“授予所有认证用户受限制的访问权限”
一、 客户端配置
回到客户端，添加远程仓库
git remote add ci_gitblit http://localhost:7070/git/ci.git
( 如果不想每次推送输入用户名和密码，可以在添加时指定：
&&git remote add ci_gitblit http://blankerer:123456@localhost:7070/git/ci.git&
看看效果：
git remote show ci_gitblit&
push本地代码：
git push ci_gitblit master
然后再看看效果：
git remote show ci_gitblit&
至此大功告成
阅读(25378) | 评论(0) | 转发(1) |
相关热门文章
给主人留下些什么吧！~~
请登录后评论。Troubleshooting
push failed for branch (n/a (unpacker error))This is a bug in JGit (). TLDR: Newer git clients are optimized to send less data on the wire. JGit expects complete data to be sent, but there are scenarios where native git can optimize-out sending objects. By default, JGit requires everything sent be complete and referenceable.If you experience this, the workaround is to temporarily disable the reachable check for the receive pack, push, and then re-enable the setting.
git.checkReferencedObjectsAreReachable = false
Eclipse/Egit/JGit complains that it "can't open upload pack"?There are a few ways this can occur:
Are you running Java 7?Java 7 introduced SNI support for SSL connections and it is enabled by default.To disable SNI alerts, add this line to your eclipse.ini file and restart Eclipse.-Djsse.enableSNIExtension=false
You are using https with a self-signed certificate and you did not configure http.sslVerify=false
Window-&Preferences-&Team-&Git-&Configuration
Click the New Entry button
Key = http.sslVerify
Value = false
Gitblit GO's default self-signed certificate is bound to localhost and you are trying to clone/push from a client based on an old version of JGit with a known flaw.
The repository is clone-restricted and you don't have access.
The repository is clone-restricted and your password changed.
A regression in Gitblit. :(
I can not push using git:// protocol on Windows using native GitThis is a long-standing, known bug in the native Git for Windows implementation.Please see
for details.
Why can't I access Gitblit GO from another machine?
Please check server.httpBindInterface and server.httpsBindInterface in gitblit.properties, you may be only be serving on localhost.
Please see the above answer about "**can't open upload pack**".
Ensure that any firewall you may have running on the Gitblit server either has an exception for your specified ports or for the running process.
How do I run Gitblit GO on port 80 or 443 in Linux?Linux requires root permissions to serve on ports & 1024.Run the server as root (security concern) or change the ports you are serving to 8080 (http) and/or 8443 (https).
Gitblit does not list my repositories?!
Confirm that the value git.repositoriesFolder in gitblit.properties actually points to your repositories folder.
Confirm that the Gitblit process has full read-write-execute permissions to your git.repositoriesFolder.
Gitblit won't open my grouped repository (/group/myrepo.git) or browse my log/branch/tag/ref?!This is likely an url encoding/decoding problem with forward slashes:bad
http://192.168.1.2/log/myrepo.git/refs/heads/master
http://192.168.1.2/log/myrepo.git/refs%2Fheads%2Fmaster
NOTE:You can not trust the url in the address bar of your browser since your browser may decode it for presentation. When in doubt, View Source of the generated html to confirm the href.There are two possible workarounds for this issue. In gitblit.properties or web.xml:
try setting web.mountParameters to false.This changes the url scheme from mounted (*/commit/myrepo.git/abcdef*) to parameterized (*/commit/?r=myrepo.git&h=abcdef*).
try changing web.forwardSlashCharacter to an asterisk or a !
Running Gitblit behind mod_proxy or some other proxy layerYou must ensure that the proxy does not decode and then re-encode request urls with interpretation of forward-slashes (*%2F*). If your proxy layer does re-encode embedded forward-slashes then you may not be able to browse grouped repositories or logs, branches, and tags unless you set web.mountParameters=false.If you are using Apache mod_proxy you may have luck with specifying .
Running Gitblit on TomcatTomcat takes the extra precaution of . This breaks Gitblit urls.You have a few options on how to handle this scenario:
Add -Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true to CATALINA_OPTS or to your JVM launch parameters
web.mountParameters = false and use non-pretty, parameterized urls
web.forwardSlashCharacter = ! which tells Gitblit to use ! instead of /
UTF-8 FilenamesTomcat also dislikes urls with non-ASCII characters. If your repositories have non-ASCII filenames you will have to modify your connector properties to allow UTF-8 encoded urls.
General Interest Questions
What kind of name is that?It's a phonetic play on
which is an image processing operation meaning bit-block transfer.
Why use Gitblit?It's a small tool that allows you to easily manage shared repositories and doesn't require alot of setup or git kung-foo.
Who is the target user for Gitblit?Small workgroups that require centralized repositories.Gitblit is not meant to be a social coding resource like
with 100s or 1000s of users. Gitblit is designed to fulfill the same function as your centralized Subversion or CVS server.
Do I need real Git?No (mostly). Gitblit is based on
which is a pure Java implementation of the .Everything you need for Gitblit (except Java) is bundled in the distribution file.
mostlyGitblit has experimental support for Garbage Collection using JGit. I have not used it enough to feel comfortable removing the EXPERIMENTAL label. It may work really well, or it may not. One thing you might consider having native git for is periodic garbage collection - when Gitblit is offline.
Can I run Gitblit in conjunction with my existing Git tooling?Yes.
Do I need a JDK or can I use a JRE?Gitblit will run just fine with a JRE.
Does Gitblit use a database to store its data?No. Gitblit stores its repository configuration information within the .git/config file and its user information in users.conf or whatever filename is configured in gitblit.properties.
Can I manually edit users.conf, gitblit.properties, or .git/config?Yes. You can manually manipulate all of them and (most) changes will be immediately available to Gitblit.Exceptions to this are noted in gitblit.properties.NOTE:Care must be taken to preserve the relationship between user roles and repository names.Please see the User Roles section of the
page for details.
Can I restrict access to branches or paths within a repository?No, not yet. Access restrictions apply to the repository as a whole.Gitblit's simple authentication and authorization mechanism can be used to facilitate one or more of the .Should you require more fine-grained access controls you might consider writing a Groovy prereceive script to block updating branch refs based on some permissions file. I would be interested in a generic, re-usable script to include with Gitblit, should someone want to implement it.Alternatively, you could use
and SSH for your repository access.
Can I authenticate users against XYZ?Yes. The user service is pluggable. You may write your own complete user service by implementing the com.gitblit.IUserService interface. Or you may subclass com.gitblit.GitblitUserService and override just the authentication. Set the fully qualified classname as the realm.userService property.
What types of Search does Gitblit support?As of 0.9.0, Gitblit supports Lucene-based searching.If Lucene indexing is disabled, Gitblit falls back to brute-force commit-traversal search. Commit-traversal search supports case-insensitive searching of commit message (default), author, and committer.To search by author or committer use the following syntax in the search box:
author: james
committer: james
Alternatively, you could enable the search type dropdown list in your gitblit.properties file.
Why did you call the setting federation.N.frequency instead of federation.N.period?!Yes, yes I know that you are really specifying the period, but Frequency sounds better to me. :)
Can Gitblit be translated?Yes. Most messages are localized to a standard Java properties file.