from svn to git (+ LDAP + password-less updates + passworded access control)
- by Jayen
We have an SVN setup and there are some things we dislike about it and some things we like about it. We want to move to git, but we're not sure exactly what setup will work for us. We're currently using SVN (w/ Authz) + Apache (w/ WebDAV & LDAP).
Hook to update the live site [like]
Live site update requires no additional interaction [like]
Live site update uses stored password [dislike]
Commits require centralized-password authentication [like]
Commit from live site changes stored credentials [dislike]
Access control (per repository) for commits [like]
Point 5 above is the one that keeps stuffing us up. Someone makes a commit from the live site and then the hook breaks.
We're thinking to use gitosis/gitolite to get access control, but as they use ssh keys, we won't be requiring passwords. We're also thinking to use git-http-backend, and use Apache for authentication, but then do we lose access control? Can the live site be automatically updated from a hook if Apache requires authentication? Can we combine git-http-backend and gitosis/gitolite somehow? Can we store http credentials with git?
