On Fri, Oct 12, 2012 at 08:12:03AM -0700, gitted wrote:
> I want to understand how to go about providing users access to git over 
> http to manage content that will be stored in their own git repository.
> Scenerio:  Users signup on a website, upon choosing an account name I will 
> create a git repository for them on my servers filesystem.
> /git/username1
> /git/username2
> I want to allow users to access their repositories over http, so they would 
> clone a repository using:
> git clone https://username1.example.com/content.git
> I don't want to force them to setup SSH, so they should have to enter their 
> username/password when connecting.
> How would I go about creating this sort of setup?  I'm confused as to how 
> them connecting via https and the mapping to their folder will work.
Not sure if that really applies, but consider looking at GitLab
(http://gitlab.org/ POSIX stack oriented) or Git Web Access
(http://gitweb.codeplex.com/ requires IIS).

Alternatively, you surely can roll something yourself, but it obviously
requires coding of a web-site engine which would take care of user
management, user access etc.  To provide access to the user's repo, it
supposedly could spawn the Git's smart HTTP backend (after performing
authentication and authorization).

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to