InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Git/Github Roundup: Ruby Books, Gems, Gitjour

Posted by Werner Schuster on Jun 19, 2008

Sections
Development,
Architecture & Design
Topics
Technology ,
Ruby on Rails ,
Ruby ,
RubyGems
Tags
Rails ,
Source Control ,
Deployment ,
Book
Github seems to be a big reason for the increasing popularity of git as SCM tool in the Ruby space, with many Ruby projects switching to using git. Github's makes it easy to watch the progress of a project (get notifications about changes) and to collaborate. Now a couple of book projects have started using Github. The books are
One of Github's features is the Ruby Gems support, which is a simple as providing a .gemspec file (and checking the "Ruby Gem" box in the Github configuration). With this, Github automatically builds the Gem when the .gemspec file is pushed. The Gem is then available by using the package source "http://gems.github.com". Since one of Github's distinguishing features is easy forking of projects, this approach could cause name clashes if different versions published a Gem. The solution to this is that the Gem name is prefixed with the username.

One benefit of git is that it pulls the full repository from a server instead of just a snapshot of the current HEAD. The repository contains the full history of the file, ie. all of the commits and versions of the past. Recently, Evan Phoenix, Chad Fowler, and Rich Kilmer used this to build gitjour, a tool that makes it easier to share git repositories on local networks. The "jour" part of the name refers to the Bonjour, Apple's name for their implementation of the Zeroconf protocol. The basic idea behind these technologies is to use multicast in local networks to advertise and consume services. As the name Zeroconf implies, it allows to add these services without having to manually find them or the host and port that offers them.

The best source to get started is Dr. Nic's tutorial to gitjour and related tools. As the article shows, with gitjour, offering a git repository is as simple as calling gitjour serve in the repository directory. On the other side, a gitjour list lists the repositories that are available on the network and gitjour clone foo clones the repository named 'foo'. For detailed installation information and more see Dr. Nic's article.

Working with Ruby and Bonjour seems to be popular, as Dr. Nic's article continues showing further tools based on the same idea, like pastejour which allows to quickly share a snippet of code or gemjour for sharing gems, and many more. The projects use the dnssd Ruby gem.

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.