Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions Makefile
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
compile:
@./rebar compile

clean:
@./rebar clean

.PHONY: compile clean
15 changes: 13 additions & 2 deletions README
Original file line number Diff line number Diff line change
Expand Up @@ -12,13 +12,24 @@ if the upload-pack takes a long time to respond (for big repos), either the
timeouts have to be increased to unreasonable values (slowing the entire
transfer down), or some connections will timeout and fail.

The above problem has actually been solved by a rewrite I (Vagabond) have
been doing as an exercise in how to improve the performance of erlang
applications. egitd is now only marginally slower than git-daemon on the
same repo, and does not suffer the timeout issues mentioned above even on
the large repos like gentoo's portage where github was having problems. I
still don't advocate its use in production, but it might be usable now.

You can see my rewrite notes here: http://andrew.hijacked.us/by_keyword/328/egit


INSTALL
-------

$ git clone git@github.com:mojombo/egitd.git
$ cd egitd
$ rake
$ make

You can also build by using ./rebar compile, which the Makefile invokes.


RUN
Expand All @@ -32,4 +43,4 @@ CONF FILE

The config file specifies the mapping between specified repo name and file location.

github.com (.+)/(.+) "/data/git/repositories/" ++ Match1 ++ "/" ++ Match2.
github.com (.+)/(.+) "/data/git/repositories/" ++ Match1 ++ "/" ++ Match2.
13 changes: 0 additions & 13 deletions Rakefile

This file was deleted.

98 changes: 0 additions & 98 deletions elibs/pipe.erl

This file was deleted.

6 changes: 0 additions & 6 deletions elibs/receive_pack.erl

This file was deleted.

Loading