4

I have an apache2 server running a virtual host with HTTPS and basic authentication enabled. The virtual host serves GIT repositories via gitweb script. Authenticated users pull repositories from virtual host.

I don't need fine access control since I am using basic authentication mechanism. Therefore, my questions are:

  1. Is gitweb the only thing I need to pull AND push changes with this setup?
  2. If not enough, do I need gitolite or gitosis to push changes?
H. Pauwelyn
  • 734
  • 4
  • 14
  • 33
David Andreoletti
  • 270
  • 3
  • 14

1 Answers1

5

gitweb is only a vizualization mechanism. You don't need it to pull/push.
A simple Apache server calling the git-http-backend mechanism is enough.

Gitolite (please, no gitosis: it is obsolete) is an authorization mechanism, also not needed to push/pull (unless you want to restrict access to a group of users).

More details in:

Community
  • 1
VonC
  • 14,433
  • 5
  • 47
  • 61
  • -To push/pull (via Smart HTTP protocol), only git-http-backend is required. -To view/restrict/enable user access; gitweb or gitolite is required. Am I right ? – David Andreoletti Jan 27 '12 at 09:44
  • @DavidAndreoletti: to view, just gitweb is required. Gitolite is only there to intercept any git command and accept or deny said command based on the user requiring access to a repo through that command. You can interface gitweb with Gitolite if you want your visualization interface to benefit from the authorization layer: http://sitaramc.github.com/gitolite/ggshb.html – VonC Jan 27 '12 at 09:54
  • In my setup, authorization layer is managed by Apache's Basic Authentication mechanism. – David Andreoletti Jan 27 '12 at 10:07
  • @DavidAndreoletti: nope: Apache's Basic Authentication, as its name suggests, is for **authentication**, NOT (I repeat *not*) authorization. Please read: http://sitaramc.github.com/gitolite/auth.html – VonC Jan 27 '12 at 10:12