« Database Design Woes ( or "Something Wicked This Way Comes") | Main | Updates, Git and Other Stuff »

07/16/2009

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Jakub Narębski

You would probably be able to drop SVK as well; it is (partially)
distributed SCM built on top of Git. Also Git can exchange commits with
Subversion (wven working as "fat client" for Subversion) using git-svn
(written in Perl).

I think self hosting is described both in "Git User's Manual" and in "Git Community Book". From what I have read a common way to set up SSH access is via Gitosis (in Ruby), but it is not the only solution.

As for web interfaces for Git there are many: gitweb (in Perl,
developed with git in git.git repository), cgit (in C), viewgit and
git-php (PHP), ginatra (Ruby and Sinatra),...

There are also more complete open source git hosting solutions: the
repo.or.cz "duct tape" (bash scripts IIRC) in repo.git or girocco.git
repository there using gitweb as web interface, Gitorious (in Ruby) fro
Gitorious.org git hosting site, InDefero (in PHP) which states that it
is meant as Google Code equiavlent for Git. There is also proprietary GitHub:FI...

P.S. It would be nice to have some Perl Monger working on Git.pm (or Git::Repo etc.), gitweb and git-svn...

http://git.or.cz/gitwiki/InterfacesFrontendsAndTools

Jakub Narębski

Why not ask on git mailing list (git@vger.kernel.org), which you can do
without subscribing, and which you can read using e.g. GMane. Or
perhaps ask Petr Baudis (of repo.or.cz), who was talking on last year
Git Together '08 meeting about working with git for some pharma company.

perigrin

We use gitosis at work for managing the repositories. It works beautifully with ssh and ssh-keys (including forwarding so that as long as git is installed on $dev_server the key from your workstation will just work). For web viewing we're using gitweb. It's not "beautiful" but it gets the job done. I've done some abortive work on a Catalyst app (see my github or find me on IRC) ... but it hasn't gotten very far yet since I don't have the time or inclination to work on it currently.Good luck with the migration.

Robin Smidsrød

I did exactly this for all of my personal projects which were stored in a big subversion repo. The repo contained approx. 90 separate (small) projects. I used gitosis for hosting the central repositories. I used git-svn to import the Subversion repo into one big git repo. I used git filter-branch subdirectory-filter to split it up into separate projects (while keeping history). Overall I'd say it has worked out very well. Web frontend I haven't decided on yet. For my school work (Java/Eclipse) I'm currently using EGit (from Google Code). EGit still has some problems, but generally it works. Since this is used on Windows I found msysgit to work without a lot of problems. I guess I should probably write an article about this.

Jakub Narębski

You would probably be able to drop SVK as well; it is (partially)
distributed SCM built on top of Git.

I'm sorry, I of course meant to say that SVK is (semi) distributed version control system built on top of Subversion (not on top of Git).

nothingmuch

Gitosis can be used to set up repository access, Gitorious is ruby app similar to Github that is open source.

For browsing code gitweb doesn't have pretty CSS but is very useful for actually extracting meaningful information. There are many other web frontends I haven't used.Lastly, I also wrote aboutmigrate from SVNusing the tools I wrote for Moose's repository.

The comments to this entry are closed.