This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
) is private.
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon () is public.
Every repository with this icon (
) is public.
commit dab76f0104653e3b4524a698264218af94ab3bdd
tree efc53c913b5ab95ecf7f983877aaacc25e2f32d1
parent ca922710714e1e727f440dbb43fa3ad4723e8aa1
tree efc53c913b5ab95ecf7f983877aaacc25e2f32d1
parent ca922710714e1e727f440dbb43fa3ad4723e8aa1
coral /
| name | age | message | |
|---|---|---|---|
 |
.gitmodules | Wed Jan 28 15:00:03 -0800 2009 | |
| |
LICENSE | Fri Nov 06 11:07:23 -0800 2009 | |
| |
README.rdoc | Wed Jan 28 05:05:15 -0800 2009 | |
 |
bin/ | Wed Jan 28 14:21:07 -0800 2009 | |
| |
lib/ | Sun Sep 27 05:50:12 -0700 2009 | |
 |
website - fa90b79 | Wed Jan 28 15:00:03 -0800 2009 |
README.rdoc
Coral distribution system
A work in progress
Coral aims to complement and — to some extent — replace RubyGems by pulling in and organizing git repositories.
Usage
Fetching a project:
$ coral clone git://github.com/wycats/thor.git
In your code:
require 'coral' require 'thor'
Why git instead of neatly packaged gems?
- with gems you have to wait for a release;
- you can’t fork a gem, contribute and push;
- publishing gems always felt dirty, admit it;
- with git you can ride an experimental branch of your favorite project;
- with git you have history.
Coral will help you maintain submodules.
Coral will help you deploy.
Did git ever get you laid?
No, and — like you — I keep wondering why is that.
