comment on

If you're running apache, adding this to your configuration will clear up the broken links-

AllowEncodedSlashes On

The other advice was good. It's a Catalyst application and there are many tutorials and guides, some in the Catalyst docs, for how to deploy them. Proxying is probably the best all around solution but fastcgi is probably the easiest. Here's a sample apache config for running one out of a user's home dir with local::lib.

  # Start gitalist with-
  # perl -Mlocal::lib=/home/moo/perl5 ~moo/Gitalist/script/gitalist_fa
+stcgi.pl -l /tmp/gitalist.socket -d
  FastCgiExternalServer /tmp/gitalist.fcgi -socket /tmp/gitalist.socke
+t
  Alias /git/ /tmp/gitalist.fcgi/
[download]

In reply to Re: running Gitalist as a sub-directory of my main web site by Your Mother
in thread running Gitalist as a sub-directory of my main web site by punkish

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Pathologically Eclectic Rubbish Lister
	PerlMonks