We can only see the first 10 commits of a certain ref at a time. the #commits supports skipping and limits to the count, so pagination should be easy.

As well as tar.gz downoads of the repo state at various commits, i think it might be an idea to be able to download a whole commit formatted as a patch. this is going to require more code than the .tar.gz archive as there is no convenience method

i forsee writing patches to the public folder so that they are cached.

Hey Guys,

Running on a MacBook Air.
Using rbenv with ruby 2.1.2p95
I followed the install directions, and when I try to run .bin/ginatra server, I get:

    /Users/keith/.rbenv/versions/2.1.2/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- ginatra (LoadError)
from /Users/keith/.rbenv/versions/2.1.2/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from ./bin/ginatra:3:in `<main>'

Here is the Gemfile.lock file

PATH
remote: .
specs:
ginatra (3.0.1)
rouge (> 0.5.3)
rugged (> 0.19.0)
sinatra (> 1.4.2)
sprockets (> 2.0)

GEM
remote: https://rubygems.org/
specs:
backports (3.6.4)
better_errors (2.0.0)
coderay (>= 1.0.0)
erubis (>= 2.6.6)
rack (>= 0.9.0)
binding_of_caller (0.7.2)
debug_inspector (>= 0.0.1)
coderay (1.1.0)
debug_inspector (0.0.2)
diff-lcs (1.2.5)
erubis (2.7.0)
hike (1.2.3)
multi_json (1.10.1)
rack (1.5.2)
rack-protection (1.5.3)
rack
rack-test (0.6.2)
rack (>= 1.0)
rake (10.4.0)
rouge (0.5.4)
rspec (3.1.0)
rspec-core (> 3.1.0)
rspec-expectations (> 3.1.0)
rspec-mocks (> 3.1.0)
rspec-core (3.1.7)
rspec-support (> 3.1.0)
rspec-expectations (3.1.2)
diff-lcs (>= 1.2.0, < 2.0)
rspec-support (> 3.1.0)
rspec-mocks (3.1.3)
rspec-support (> 3.1.0)
rspec-support (3.1.2)
rugged (0.19.0)
sinatra (1.4.5)
rack (> 1.4)
rack-protection (> 1.4)
tilt (> 1.3, >= 1.3.4)
sinatra-contrib (1.4.2)
backports (>= 2.0)
multi_json
rack-protection
rack-test
sinatra (> 1.4.0)
tilt (> 1.3)
sprockets (2.12.3)
hike (> 1.2)
multi_json (> 1.0)
rack (> 1.0)
tilt (~> 1.1, != 1.3.0)
tilt (1.4.1)

PLATFORMS
ruby

DEPENDENCIES
better_errors
binding_of_caller
ginatra!
rack-test
rake
rspec
sinatra-contrib

web demo not working

i think we need support of more than just the master branch.

When file contain unicode, such as chinese, Ginatra will get "500 Internal Server Error". and commit information contain unicode, Ginatra also get "500 Internal Server Error".

Why?

• Rake tasks for demo [raggi]
• Rake tasks for adding repos [lenary]

The clone url for projects do not reflect the protocol used for my site.

I have ginatra deployed using https (http is redirected to https on the reverse proxy in front of ginatra); however, the clone url remains as "git clone http://...my dns name...".

I would suggest a configuration option to specify the clone protocol (e.g. http/https/ssh/etc).

I've tried using ginatra as a gem and by cloning the repository and I get the same error when I run 'ginatra server start':

/Users/umjames/Documents/Development/Projects/open_source/ginatra/bin/../lib/ginatra.rb:1:in `require': no such file to load -- sinatra/base (LoadError)
    from /Users/umjames/Documents/Development/Projects/open_source/ginatra/bin/../lib/ginatra.rb:1
    from ./ginatra:5:in `require'
    from ./ginatra:5

I have the following relevant gems installed:

coderay (0.8.357)
cucumber (0.5.3)
grit (2.0.0)
jeweler (1.4.0)
git (1.2.5)
kematzy-sinatra-cache (0.2.2)
mongrel (1.1.5)
rack (1.0.1, 0.9.1)
rake (0.8.7, 0.8.3, 0.8.1)
rspec (1.2.9)
sinatra (0.9.4)
vegas (0.1.1)

Running 'gem env' gives:

RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.5
  - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-10
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/umjames/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gems.rubyforge.org/", "http://gems.github.com/"]
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/
     - http://gems.github.com/

Is there a specific directory I'm supposed to be running 'ginatra server start' from?

If you have any problems with ginatra, esp with respect to the branches, post your problems here.

Just FYI, I did the following renames which github didn't like at all (i had to use -f when pushing):

master -> old_master
classy -> master

This said, it ushers in a new era of ginatra now being classy. We're working on commands for ginatra, and it will be becoming a gem pretty soon. Stay Posted for more news.

We now have a twitter feed: http://twitter.com/ginatra and updates periodically appear on my blog: http://lenary.co.uk/

None are showing up on Heroku, or when i use Passenger. Needs investigation

Multiple directory or glob-based repo paths

Suggested by raggi

Hi,

I'm not sure this project is still up... But I've got a little issue with my Htaccess file.

The Ginatra server is running on my web hoster localhost:64881 by running the Ginatra gem. So I try a redirect from my webspace to the server.

The Htaccess file looks like this:

RewriteEngine On
RewriteBase /
RewriteRule (.*) http://localhost:64881/$1 [P,L]

But when I open the site it shows only: Not Found: /

Do you know, what I do wrong?

When I clone the ginatra repo and run the rspecs I get failures. Do the rspecs expect there to be a "test" repo somewhere? I see hashes in the rspecs, e.g. "it returns a link for a commit patch" helpers_spec.rb:67, so presumably there are some pre-existing commits by a specific user that need to be in that repo (i.e. I can't just git init and add some commits myself)?

How to resolve 500 error

I got some errors during install:

% irb -r 'rubygems' -r 'rubygems'
ruby-1.9.2-p180 :001 > Ginatra::Config.setup!
NameError: uninitialized constant Object::Ginatra
from (irb):1
from /home/sonia/.rvm/rubies/ruby-1.9.2-p180/bin/irb:16:in `

Would you be able to include a sample ~/.ginatra/config.yml in the repo, to help get around these problems?

My full config:

% rvm info

ruby-1.9.2-p180:

system:
uname: "Linux zapote 2.6.38-10-generic-pae #46-Ubuntu SMP Tue Jun 28 16:54:49 UTC 2011 i686 i686 i386 GNU/Linux"
bash: "/bin/bash => GNU bash, version 4.2.8(1)-release (i686-pc-linux-gnu)"
zsh: "/usr/bin/zsh => zsh 4.3.11 (i686-pc-linux-gnu)"

rvm:
version: "rvm 1.6.20 by Wayne E. Seguin ([email protected]) [https://rvm.beginrescueend.com/]"

ruby:
interpreter: "ruby"
version: "1.9.2p180"
date: "2011-02-18"
platform: "i686-linux"
patchlevel: "2011-02-18 revision 30909"
full_version: "ruby 1.9.2p180 (2011-02-18 revision 30909) [i686-linux]"

homes:
gem: "/home/sonia/.rvm/gems/ruby-1.9.2-p180"
ruby: "/home/sonia/.rvm/rubies/ruby-1.9.2-p180"

binaries:
ruby: "/home/sonia/.rvm/bin/ruby"
irb: "/home/sonia/.rvm/bin/irb"
gem: "/home/sonia/.rvm/bin/gem"
rake: "/home/sonia/.rvm/bin/rake"

environment:
PATH: "/home/sonia/.rvm/bin:/home/sonia/.rvm/gems/ruby-1.9.2-p180/bin:/home/sonia/.rvm/gems/ruby-1.9.2-p180@global/bin:/home/sonia/.rvm/rubies/ruby-1.9.2-p180/bin:/home/sonia/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/var/lib/gems/1.8/bin:/usr/lib/jvm/java-6-sun/jre/bin"
GEM_HOME: "/home/sonia/.rvm/gems/ruby-1.9.2-p180"
GEM_PATH: "/home/sonia/.rvm/gems/ruby-1.9.2-p180:/home/sonia/.rvm/gems/ruby-1.9.2-p180@global"
MY_RUBY_HOME: "/home/sonia/.rvm/rubies/ruby-1.9.2-p180"
IRBRC: "/home/sonia/.rvm/rubies/ruby-1.9.2-p180/.irbrc"
RUBYOPT: ""
gemset: ""

% rvm gem list -l

*** LOCAL GEMS ***

rake (0.8.7)

*** LOCAL GEMS ***

abstract (1.0.0)
actionmailer (3.0.9)
actionpack (3.0.9)
activemodel (3.0.9)
activerecord (3.0.9)
activeresource (3.0.9)
activesupport (3.0.9)
arel (2.0.10)
builder (3.0.0, 2.1.2)
bundler (1.0.15)
diff-lcs (1.1.2)
erubis (2.7.0, 2.6.6)
ginatra (2.3.0)
grit (2.4.1)
i18n (0.5.0)
mail (2.2.19)
mechanize (2.0.1)
mime-types (1.16)
net-http-digest_auth (1.1.1)
net-http-persistent (1.8)
nokogiri (1.5.0)
polyglot (0.3.1)
rack (1.2.3)
rack-mount (0.6.14)
rack-test (0.5.7)
rails (3.0.9)
railties (3.0.9)
rake (0.9.2, 0.8.7)
rdoc (3.8)
sinatra (1.2.6)
sqlite3 (1.3.3)
thor (0.14.6)
tilt (1.3.2)
treetop (1.4.9)
tzinfo (0.3.29)
vegas (0.1.8)
webrobots (0.0.10)

The readme is probably wrong and needs updating.

Git changed what it put in .git/description when you cloned a repo between 1.5.x and 1.6.3 - this is known to break some cucumber features. Radar suggested use File.readlines to dynamically find what git.description should be.

Ginatra gently refuses to work properly when installed on http://domain.com/ginatra

Hi,

if a simple .txt file contains (german) Umlaute like äöüÄÖÜ or ß in the file content or in the file name, Ginatra is not able to show the commit detail of a commit. It displays then:
"500 Internal Server Error

Sorry, something went wrong."

The file encoding was tested with ANSI and UTF-8 (same problem with both).
If you click on the source, the file content of .txt files with Umlaute won't be shown directly (but as binary file download or raw possible).

(Umlaute in the commit comment itsself doesn't seem to make any problems.)

Thank you very much! Ginatra is great!

The ginatra binary command currently just starts a ginatra instance,

this is all about to change. after discussion, we have decided on:

ginatra add - adds the current directory into what is served by ginatra, or if there is no .git directory, checks each of the subdirectories for a .git directory and adds them all into ginatra
ginatra serve - starts the ginatra server
ginatra daemon add / ginatra daemon remove - to say which ones are served by a git-daemon

i'll think of more later

gonna use git-style-binaries gem i think

127.0.0.1 - - [04/Dec/2009 13:09:25] "GET / HTTP/1.1" 200 3624 0.0063
127.0.0.1 - - [04/Dec/2009 13:09:25] "GET /src/index.css HTTP/1.1" 200 1685 0.0037
127.0.0.1 - - [04/Dec/2009 13:09:25] "GET /src/highlight.pack.js HTTP/1.1" 200 77444 0.0012
127.0.0.1 - - [04/Dec/2009 13:09:25] "GET /src/default.css HTTP/1.1" 200 1731 0.0006
127.0.0.1 - - [04/Dec/2009 13:09:25] "GET /src/jquery-1.3.2.min.js HTTP/1.1" 200 57254 0.0009
127.0.0.1 - - [04/Dec/2009 13:09:25] "GET /src/reset.css HTTP/1.1" 200 1026 0.0019
127.0.0.1 - - [04/Dec/2009 13:09:25] "GET /src/type.css HTTP/1.1" 200 506 0.0011
127.0.0.1 - - [04/Dec/2009 13:09:25] "GET /src/colour.css HTTP/1.1" 200 1939 0.0017
127.0.0.1 - - [04/Dec/2009 13:09:25] "GET /src/commit.css HTTP/1.1" 200 3008 0.0008
127.0.0.1 - - [04/Dec/2009 13:09:25] "GET /src/lists.css HTTP/1.1" 200 316 0.0006
127.0.0.1 - - [04/Dec/2009 13:09:25] "GET /src/table.css HTTP/1.1" 200 463 0.0006
127.0.0.1 - - [04/Dec/2009 13:09:25] "GET /src/ginatra.js HTTP/1.1" 200 236 0.0008
127.0.0.1 - - [04/Dec/2009 13:09:25] "GET /favicon.ico HTTP/1.1" 200 - 0.0007

i think something needs done about this really. I count 13 http requests. That's at least 9 too many for a production environment.

When browsing through the commits, sometimes rendering would fail with

incompatible character encodings: ASCII-8BIT and UTF-8
file: commit.erb location: block (2 levels) in singletonclass line: 63

Testing on ruby 1.9.3p0 (2011-10-30 revision 33570) [arm-linux-eabihf].

I poked around a bit and found out it's quite a common issue (http://stackoverflow.com/questions/10341550/incompatible-character-encoding-in-simple-sinatra-app).
As most of my sources/comments/commit messages have non-ascii characters I decided to look for a nice/easy way to fix it. At the moment, what I've done is to do a force_encoding 'binary' on each string being included in the .erb and it seems to be working.
I could go through all templates but I wanted to ask if anyone has a better solution before I send a pull request.

we have a constant called Config in our Ginatra module that loads a config from a specified file, which will probably become ~/.ginatra (the file will just be yaml)

Hey, thanks for this!
I used to use this a while back, always worked fine, just re-installed and now its shows no repos (just the name/title), I have a repo in default directory (~/repos) not showing, so I copied the default config.yml from ginatras repo as ~/.ginatra/config.yml and changed git_dirs to where I keep all of my repos (~/pkgs), here I have 30-40 repos, still none show in the browser.
Thanks again.

it's broken. specifically ginatra-server. this displeases me, as i am getting NO useful error messages. would be nice in all honesty.

Shouldn't be so hard, but needs other things to happen first

Self explanatory really. only per-project needed i think

These really don't look so hard, so i think i'll implement them on top of the refs functionality sometime in the future, using Grit::Repo#archive_tar_gz

I think the next thing that ginatra really needs is a file viewer. i'll get onto it.

probably will use highlight.js and remove dependency on coderay, so that everything is more versatile.

This is two different but linked pieces.

the first is a small box/table on the log page that contains links to each ref: so Heads/branches under one header, then tags below another header underneath, and perhaps remotes, but i'm as yet undecided about them

the second is that in our list of commits in the log, if say commit aade37 is tagged as 1.0.3, there is a small box in the log table that says this. the same applies for other refs and tags

mattn found a bug with the repo description hiding if you edited the description file:

fix here: http://gist.github.com/130573

i'll do it tonight, no time now.

I've installed ginatra on my cubietruck running under cubian:

Linux cubietruck 3.4.79-sun7i #19 SMP PREEMPT Fri Oct 10 03:20:03 CST 2014 armv7l GNU/Linux

gem install was successful.
But when I try to run ginatra by ginatra run I have next output:

ginatra run
/var/lib/gems/1.9.1/gems/ginatra-4.0.2/config.ru:17:in `block in <main>': uninitialized constant MakeMakefile (NameError)
        from /var/lib/gems/1.9.1/gems/rack-1.6.0/lib/rack/builder.rb:55:in `instance_eval'
        from /var/lib/gems/1.9.1/gems/rack-1.6.0/lib/rack/builder.rb:55:in `initialize'
        from /var/lib/gems/1.9.1/gems/ginatra-4.0.2/config.ru:in `new'
        from /var/lib/gems/1.9.1/gems/ginatra-4.0.2/config.ru:in `<main>'
        from /var/lib/gems/1.9.1/gems/rack-1.6.0/lib/rack/builder.rb:49:in `eval'
        from /var/lib/gems/1.9.1/gems/rack-1.6.0/lib/rack/builder.rb:49:in `new_from_string'
        from /var/lib/gems/1.9.1/gems/rack-1.6.0/lib/rack/builder.rb:40:in `parse_file'
        from /var/lib/gems/1.9.1/gems/rack-1.6.0/lib/rack/server.rb:299:in `build_app_and_options_from_config'
        from /var/lib/gems/1.9.1/gems/rack-1.6.0/lib/rack/server.rb:208:in `app'
        from /var/lib/gems/1.9.1/gems/rack-1.6.0/lib/rack/server.rb:336:in `wrapped_app'
        from /var/lib/gems/1.9.1/gems/rack-1.6.0/lib/rack/server.rb:272:in `start'
        from /var/lib/gems/1.9.1/gems/rack-1.6.0/lib/rack/server.rb:147:in `start'
        from /var/lib/gems/1.9.1/gems/rack-1.6.0/bin/rackup:4:in `<top (required)>'
        from /usr/local/bin/rackup:23:in `load'
        from /usr/local/bin/rackup:23:in `<main>'
Ginatra runs on localhost:9797

config.yml:

# Default config file for Ginatra
# Settings specified in '~/.ginatra/config.yml' will take precedence over these
git_dirs:
  - /mnt/media/Repositories/*
sitename: Ginatra
description: "My Git Repositories"
port: 9797
host: localhost
prefix: "/"
git_clone_enabled?: true

I just installed ginatra v4.0.0 as per the readme instructions. Upon trying ginatra run, I am greeted with:

...
/usr/local/rvm/rubies/ruby-2.0.0-p451/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- better_errors (LoadError
...

After installing better_errors with gem install better_errors, I now get:

...
/usr/local/rvm/rubies/ruby-2.0.0-p451/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- sinatra/reloader (LoadError)
....

Looks like ginatra's Gemfile may be missing some entries.

I'm on ruby-2.0.0p451 on Ubuntu 12.04 under rvm with ginatra gemset.

Radar also suggested have a new design. I'm willing to let someone hack away at it, but at the same time i think it's fine as it is. I need to sort out a few things like ie png fixes and other clever things, but that shouldn't be so hard.

if we are having a redesign, i'd like it to be as light as github's design, rather than any darker - maybe i should abstract out all the colours from my css into a single file that can be interchanged at will. ideas ideas ideas

Hey there,

I just installed the Ginatra 4.0.2 app. I changed the config.yml in the root folder and when I type

sudo ginatra run

I get

checking for git... yes
Ginatra runs on xxx.xxx.xxx.xxx:9797

But when I use

sudo ginatra status

I get back

Ginatra is NOT running

What am I doing wrong? My config file looks like:

git_dirs:
  - /opt/git/*
description: "My Git Repositories"
port: 9797
host: xxx.xxx.xxx.xxx
prefix: "/"
git_clone_enable?: true

My app is installed under /usr/local/lib/ruby/gems/2.2.0/gems/ginatra-4.0.2 should this be the prefix?

EDIT: I got the server running atm but I'm getting a 500 interal server error. I double checked my git_dirs and it seems ok... it's still on /opt/git/* and I've got only one repo on my server which is: /opt/git/c-programming.git. I've played a little with the git_dirs parameter and even if I complete change it to some random location ginatra still says: "checking for git...yes"

I have a rather standard gitolite git system setup. After setting ginatra up and setting the git_dirs to my ~/repositories directory I found all repos were exposed. This can easily be changed/limted by creating a new directory and symlinking to the repos you want to expose.

For Example:

• git_root: ~/repositories
• public git repositories: ~/repos-public

In ~/repos-public:

• ln -s ../repositories/testing.git
  Now change the git_dirs config setting to use ~/repos-public and you will only see the testing.git repo.

pictures or it didn't happen ;)

could you add some screenshots of the UI to the readme?

i think we need support of more than just the master branch.