package Gitalist;
use Moose;
BEGIN { require 5.008006; }
-use Catalyst::Runtime 5.80;
+use Catalyst::Runtime 5.90006;
+use Gitalist::Git::Util;
use namespace::autoclean;
extends 'Catalyst';
SubRequest
/;
-our $VERSION = '0.003004';
+our $VERSION = '0.004002';
$VERSION = eval $VERSION;
__PACKAGE__->config(
if ($ctx->req->param('a')) {
$ctx->req->uri->path("/legacy$path");
}
-
+
if($path =~ s/[.]json$// && $ctx->req->content_type eq 'application/json') {
$ctx->req->uri->path($path);
}
my $uri = $self->request->uri_with(@args);
# Wow this awful.
$uri =~ s[/fragment\b][];
- return $uri;
+ return $uri;
}
+after setup_finalize => sub {
+ # At app startup, ensure we can find a git binary, rather than
+ # lazily breaking later at request time.
+ Gitalist::Git::Util->new->_git; # FIXME - should not be a private method
+};
+
1;
__END__
The Gitalist config is loaded with L<Catalyst::Plugin::ConfigLoader>
and the available config options are:
-=head2 Model::CollectionOfRepos
-
=over
-=item git
+=item no_gravatars
+
+If true don't display gravatars. May be desirable if you are worried about
+leaking repo names via the browser referer headers.
+
+=back
+
+=head2 Model::CollectionOfRepos
-Path to the C<git> binary.
+=over
=item repo_dir
If provided every must contain a file of the same name to be
visible. This is similar to C<gitweb>'s functionality.
+=item class
+
+If you want a different way of surfacing repositories you can use your
+own model (i.e something that composes
+L<Gitalist::Git::CollectionOfRepositories>) and specify the class name with
+this config option.
+
+=item args
+
+Any additional arguments to be passed into the Model constructor, only
+of use when used in conjunction with C<class> (see above).
+
=back
=head2 paging