From: "Jakub Narębski" <jnareb@gmail.com>
To: "Trenton D. Adams" <trenton.d.adams@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git instaweb - share all project files
Date: Wed, 10 Apr 2013 19:03:23 +0200 [thread overview]
Message-ID: <51659B5B.6000707@gmail.com> (raw)
In-Reply-To: <CAMg8Y2pFXrbh8cz6m5z=LsksRijLVcV4fTk-TBx+9yaQTtAzpA@mail.gmail.com>
W dniu 07.04.2013 05:02, Trenton D. Adams pisze:
> On that first page that shows up, it shows the .git folder. It would
> be kind of nice if it shared out both the git repo and the actual
> current project files. I frequently have stuff I'd like to see in a
> web browser, and even requires one (i.e. Navigating to
> file:///home/blah/blah doesn't work; ajax requests for example)
There are a few possible solutions, from simplest to most complicated:
1. Configure gitweb ran by git-instaweb to have 'worktree' link in
the action bar pointing to 'file:///path/to/repo' (or rather
'file:///path/to/workdir') via 'actions' feature, adding e.g.
$feature{'actions'}{'default'} =
[('worktree', 'file:///path/to/repo', 'summary')];
to gitweb_config.perl / gitweb.conf used by git-instaweb's gitweb.
This of course works only for local use, so either git-instaweb
or gitweb (in config) should check that we use it locally
(e.g. if hostname is 'localhost' or equivalent).
2. In the web server configuration generated by git-instaweb, perhaps
as an option, add serving of worktree (with mod_autoindex aka.
'Options +Indexes' for Apache2, and equivalent solutions for *all*
other supported web servers: lighttpd, mongoose, plack, webrick).
This may require some fiddling with URI rewriting, or change of
gitweb URI, to be able to have both worktree index and gitweb
script (gitweb is now under '/'), so it should probably be protected
by an option to git-instaweb.
3. Add proper support to gitweb: add 'worktree' action (similar to
'tree' action / view). Probably needs to be made somewhat
configurable (and of course enabled in git-instaweb).
Unfortunately solution 1.) which is simplest is not enough for your
situation...
I can add 3.) to my gitweb TODO, but I don't know when I would be able
to get to implementing it.
--
Jakub Narębski
next prev parent reply other threads:[~2013-04-10 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 3:02 git instaweb - share all project files Trenton D. Adams
2013-04-10 17:03 ` Jakub Narębski [this message]
2013-04-10 22:42 ` Trenton D. Adams
2013-04-13 15:21 ` Jakub Narębski
2013-04-13 20:02 ` Eric Wong
2013-04-14 10:35 ` Jakub Narębski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51659B5B.6000707@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=trenton.d.adams@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.