中文请参考:
http://blog.longwin.com.tw/2009/05/build-git-env-over-http-2009/
Since Apache is one of those packages people like to compile
themselves while others prefer the bureaucrat's dream Debian, it is
impossible to give guidelines which will work for everyone. Just send
some feedback to the mailing list at git@vger.kernel.org to get this
document tailored to your favorite distro.
What's needed:
- Have an Apache web-server
On Debian:
$ apt-get install apache2
To get apache2 by default started,
edit /etc/default/apache2 and set NO_START=0
- can edit the configuration of it.
This could be found under /etc/httpd, or refer to your Apache documentation.
On Debian: this means being able to edit files under /etc/apache2
- can restart it.
'apachectl --graceful' might do. If it doesn't, just stop and
restart apache. Be warning that active connections to your server
might be aborted by this.
On Debian:
$ /etc/init.d/apache2 restart
or
$ /etc/init.d/apache2 force-reload
(which seems to do the same)
This adds symlinks from the /etc/apache2/mods-enabled to
/etc/apache2/mods-available.
- have permissions to chown a directory
- have git installed at the server _and_ client
In effect, this probably means you're going to be root.
Step 1: setup a bare GIT repository
-----------------------------------
At the time of writing, git-http-push cannot remotely create a GIT
repository. So we have to do that at the server side with git. Another
option would be to generate an empty repository at the client and copy
it to the server with WebDAV. But then you're probably the first to
try that out :)
Create the directory under the DocumentRoot of the directories served
by Apache. As an example we take /usr/local/apache2, but try "grep
DocumentRoot /where/ever/httpd.conf" to find your root:
$ cd /usr/local/apache/htdocs
$ mkdir my-new-repo.git
On Debian:
$ cd /var/www
$ mkdir my-new-repo.git
Initialize a bare repository
$ cd my-new-repo.git
$ git --bare init
Change the ownership to your web-server's credentials. Use "grep ^User
httpd.conf" and "grep ^Group httpd.conf" to find out:
$ chown -R www.www .
On Debian:
$ chown -R www-data.www-data .
If you do not know which user Apache runs as, you can alternatively do
a "chmod -R a+w .", inspect the files which are created later on, and
set the permissions appropriately.
Restart apache2, and check whether http://server/my-new-repo.git gives
a directory listing. If not, check whether apache started up
successfully.
Step 2: enable DAV on this repository
-------------------------------------
First make sure the dav_module is loaded. For this, insert in httpd.conf:
LoadModule dav_module libexec/httpd/libdav.so
AddModule mod_dav.c
Also make sure that this line exists which is the file used for
locking DAV operations:
DAVLockDB "/usr/local/apache2/temp/DAV.lock"
On Debian these steps can be performed with:
Enable the dav and dav_fs modules of apache:
$ a2enmod dav_fs
(just to be sure. dav_fs might be unneeded, I don't know)
$ a2enmod dav
The DAV lock is located in /etc/apache2/mods-available/dav_fs.conf:
DAVLockDB /var/lock/apache2/DAVLock
Of course, it can point somewhere else, but the string is actually just a
prefix in some Apache configurations, and therefore the _directory_ has to
be writable by the user Apache runs as.
Then, add something like this to your httpd.conf
DAV on
AuthType Basic
AuthName "Git"
AuthUserFile /usr/local/apache2/conf/passwd.git
Require valid-user
On Debian:
Create (or add to) /etc/apache2/conf.d/git.conf :
DAV on
AuthType Basic
AuthName "Git"
AuthUserFile /etc/apache2/passwd.git
Require valid-user
Debian automatically reads all files under /etc/apach2/conf.d.
The password file can be somewhere else, but it has to be readable by
Apache and preferably not readable by the world.
Create this file by
$ htpasswd -c /usr/local/apache2/conf/passwd.git
On Debian:
$ htpasswd -c /etc/apache2/passwd.git
You will be asked a password, and the file is created. Subsequent calls
to htpasswd should omit the '-c' option, since you want to append to the
existing file.
You need to restart Apache.
Now go to http://@/my-new-repo.git in your
browser to check whether it asks for a password and accepts the right
password.
On Debian:
To test the WebDAV part, do:
$ apt-get install litmus
$ litmus http:///my-new-repo.git
Most tests should pass.
A command line tool to test WebDAV is cadaver.
If you're into Windows, from XP onwards Internet Explorer supports
WebDAV. For this, do Internet Explorer -> Open Location ->
http:///my-new-repo.git [x] Open as webfolder -> login .
Step 3: setup the client
------------------------
Make sure that you have HTTP support, i.e. your git was built with curl.
The easiest way to check is to look for the executable 'git-http-push'.
Then, add the following to your $HOME/.netrc (you can do without, but will be
asked to input your password a _lot_ of times):
machine
login
password
...and set permissions:
chmod 600 ~/.netrc
If you want to access the web-server by its IP, you have to type that in,
instead of the server name.
To check whether all is OK, do:
curl --netrc --location -v http://@/my-new-repo.git/
...this should give a directory listing in HTML of /var/www/my-new-repo.git .
Now, add the remote in your existing repository which contains the project
you want to export:
$ git-config remote.upload.url \
http://@/my-new-repo.git/
It is important to put the last '/'; Without it, the server will send
a redirect which git-http-push does not (yet) understand, and git-http-push
will repeat the request infinitely.
Step 4: make the initial push
-----------------------------
From your client repository, do
$ git push upload master
This pushes branch 'master' (which is assumed to be the branch you
want to export) to repository called 'upload', which we previously
defined with git-config.
Troubleshooting:
----------------
If git-http-push says
Error: no DAV locking support on remote repo http://...
then it means the web-server did not accept your authentication. Make sure
that the user name and password matches in httpd.conf, .netrc and the URL
you are uploading to.
If git-http-push shows you an error (22/502) when trying to MOVE a blob,
it means that your web-server somehow does not recognize its name in the
request; This can happen when you start Apache, but then disable the
network interface. A simple restart of Apache helps.
Errors like (22/502) are of format (curl error code/http error
code). So (22/404) means something like 'not found' at the server.
Reading /usr/local/apache2/logs/error_log is often helpful.
On Debian: Read /var/log/apache2/error.log instead.
Debian References: http://www.debian-administration.org/articles/285
Authors
Johannes Schindelin
Rutger Nijlunsing
分享到:
相关推荐
Git-2.21.0-64 for windows Git 2.23 Release Notes ====================== Updates since v2.22 ------------------- Backward compatibility note * The "--base" option of "format-patch" computed the ...
.git-bisect works properly even when versions of the binary files change over time. (We recommend installing a git-sym-post-checkout-hook, in case the resources have not been cached already.)selective...
全部HTTP 通过http端点访问各种资源(nfs,smb,ssh,http / dav,git,docker)的统一接口。 集成始终提供最新内容的代理。 在不同的层上启用访问限制。 HTTP:基本身份验证,IP地址资源:每资源acl安装/运行拉最新...
GitLab外壳 GitLab Shell为GitLab处理git SSH会话 GitLab Shell为GitLab处理git SSH会话并修改授权密钥列表... git over SSH-> gitlab-shell-> API调用gitlab-rails(Authorization)->接受或拒绝->建立Gitaly会话 git
要从源代码构建godoh ,请执行以下步骤: 确保您拥有Go 1.13+ 使用git clone https://github.com/sensepost/goDoH.git克隆此存储库运行生成make key以生成用于通信的唯一加密密钥使用以下选项之一构建项目: go ...
先决条件: ...运行git clone https://github.com/romaneul/sh-over-avs-demo.git cd sh-over-avs-demo npm install 更新.env文件: LWA_CLIENT_ID= LWA_CLIENT_SECRET=<LWA Client Secret from
http://git.savannah.gnu.org/cgit/lwip/lwip-contrib.git Submit patches and bugs via the lwIP project page: http://savannah.nongnu.org/projects/lwip/ Continuous integration builds (GCC, clang): ...
Machines discovery/mapping (over Wifi) and port scan (over 3G/Wifi) utility for Android devices. Features Discover Machines on a LAN (connect/ping discovery, dns discovery) TCP Port Scanner (connect...
var client = Stomp.over(ws); // 定义连接成功回调函数 var on_connect = function(x) { //data.body是接收到的数据 client.subscribe("/queue/default", function(data) { var msg = data.body; alert(...
JSON-RPC (over HTTP and WebSocket)/XML-RPC interface Run as a daemon process Selective download in multi-file torrent/Metalink Chunk checksum validation in Metalink Can disable segmented ...
{ :name => "SPANISH" , :code => "es" , :reliable => true }来源获取用于编译ext/lib/libcld2.so和ext/lib/libcld2_full.so # Non-members may check out a read-only working copy anonymously over HTTP.svn che
There are reports that the tool does not work over an RDP session. The tool is actually a merge of 2 previous tools; RunAsSystem and RunFromToken. The curious ones might notice that RunFromToken is...
您是说吗?sipjs.com SIP.js开发人员文档 如果您正在寻找SIP.js github页面,则可以...发展git clone ...over localhost:3000bundle exec guard # live rebuildPublish to Gitlab Pages: git push origin masterPublish t
PageHelper | MyBatis物理分页插件 | [http://git.oschina.net/free/Mybatis_PageHelper](http://git.oschina.net/free/Mybatis_PageHelper) Druid | 数据库连接池 | [https://github.com/alibaba/druid]...
rtop 是一个简单的无代理的远程服务器监控工具,基于 SSH 连接进行工作。... refresh interval in seconds (default: 5)下载并构建:git clone --recursive http://github.com/rapidloop/rtop cd rtop make
它使用 REST over HTTP 与 API 通信。 这些共同为 Web 应用程序开发提供了一种非常快速、React性和简单的方法,并且作为一个团队完成了这个项目,对我们来说做得非常好。 安装 git clone git@
画中画:视频视频元素上的演示。 画中画目前仅适用于视频元素。 画中画目前在Chrome 69中位于浏览器标志的后面,因此您必须启用其中的一些标志才能使演示...Serve files over HTTP, e.g.$ python -m SimpleHTTPServer
git clone http://www.denx.de/git/u-boot.git u-boot/ git clone rsync://www.denx.de/git/u-boot.git u-boot/ 5.2 源代码包的解压 如果你是通过CVS得到的U-Boot源代码,你可以跳过这一步,因为你得到的已经是解压...
Focused on deployment, viability, and maintainability, you will learn the use of Eclipse, Maven, and Git. You will walk through the separation of concerns driven by the microservices principles. ...
51. Monitoring and Management over HTTP 51.1. Customizing the Management Endpoint Paths 51.2. Customizing the Management Server Port 51.3. Configuring Management-specific SSL 51.4. Customizing the ...