Gritano

Gritano is the simplest way to configure a git server over ssh. You can create repositories and manage user access using this practical tool.

Requirements

ruby 1.9 or 2.0 (www.ruby-lang.org)
git (git-scm.com)

Install

$ gem install gritano

Update

If you are using a previous version, you should update your instalation:

$ gem install gritano

$ gritano setup:install

Usage

First of all you should create a git user who will be responsible for store and manipulate repositories. Lets suppose we are logged as this user.

All you need to do to set up Gritano is

$ gritano setup:prepare && gritano setup:install

After that you can add users:

$ gritano user:add igorbonadio

add administrator rights to this user:

$ gritano user:admin:add igorbonadio

add user’s public keys:

$ gritano user:key:add igorbonadio mykey < id_rsa.pub

create bare repositories:

$ gritano repo:add proj.git

and control access:

$ gritano repo:read:add proj.git igorbonadio

For more information, execute

$ gritano help

User Access

Gritano 0.2.0 introduced a new feature that enables users to execute some simple commands via ssh:

$ ssh [email protected] username

$ ssh [email protected] repo:list

$ ssh [email protected] key:list

$ ssh [email protected] key:add mykey < id_rsa.pub

$ ssh [email protected] key:add mykey

For more information, execute

$ ssh [email protected] help

Admin Access

Starting from Gritano 0.3.0, administrators can execute commands via ssh:

$ ssh [email protected] admin:user:add username

$ ssh [email protected] admin:user:rm username

$ ssh [email protected] admin:user:key:add username keyname < key.pub

$ ssh [email protected] admin:user:key:rm username keyname

$ ssh [email protected] admin:repo:add reponame.git

$ ssh [email protected] admin:repo:rm reponame.git

$ ssh [email protected] admin:repo:list

For more Information

igorbonadio.com.br/gritano

Contributing to Gritano

Check out the latest master to make sure the feature hasn’t been implemented or the bug hasn’t been fixed yet.
Check out the issue tracker to make sure someone already hasn’t requested it and/or contributed it.
Fork the project.
Start a feature/bugfix branch.
Commit and push until you are happy with your contribution.
Make sure to add tests for it. This is important so I don’t break it in a future version unintentionally.
Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.