I have been playing around with git. One of the things I am trying to do right now is set up a central repository. I have seen various tutorials on the web for using gitosis and gitweb to set up a central git repository with HTTP read/browse access and ssh update access. But what I am wondering is if there is any way of getting update access via HTTP/HTTPS? So far I have not been able to find anything on that.
Additional ramblings that can be ignored:
Access via ssh is problematic - a snowball has a better chance in hell that what I would have convincing the corporate IT folks to open port 22 in the firewall. I recall ages ago that when I needed access to public CVS repository that corporate IT installed an extra PC outside the corporate firewall for me to use just for the CVS access. I was so happy when that repository moved to Subversion with HTTP/HTTPS access (and now I have seen posts where that team is looking at git. sigh).
As an aside, I set up a Mercurial central repo with HTTP/HTTPs access without too many problems (well, I was setting it up on Windows and following Linux instructions and getting weird errors whose googled suggested solutions were were "build Mercurial from source", but once I understood what Python was complaining about the solution was actually very simple).
That was one of the options I was considering, but I would like to try a pure Git play. Also, I think that having a centralized repository such as Subversion in the mix reduces some of the benefits of using a distributed repository.
Well, the Subversion/Git pairing concept wasn't intended to supplant Git or the concept of a central repository. It was intended to allow people to keep a local repository for their own work independent of the repositories that other people might be using (especially if their Internet connections were sporadic). Then when you've got something worthy of a major commit, you push the Subversion back to the central Git repo.
Of course, if you're dealing with a large, unruly pack of relatively undisciplined maybe-committers, it also keeps clutter out of the central repo when people start something and then don't finish it. Linux Torvalds has problems beyond the worst nightmares of most of us.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com