From: Mircea Bardac <dev.list@mircea.bardac.net>
To: git@vger.kernel.org
Subject: gitweb on shared hosting
Date: Sat, 2 Jun 2007 19:53:08 +0300 [thread overview]
Message-ID: <200706021953.09942.dev.list@mircea.bardac.net> (raw)
Hi everybody,
I don't know if this is possible or not, but I'm trying with no results.
Is it possible to install gitweb on a shared hosting system, with no root
access. Reading the INSTALL document reveals only information for
configuration on build-time/install as root.
I expected it to be installable just as any other web application:
* get gitweb.cgi and related files + place them on the webserver
* modify a config file (gitweb.cgi) to update the paths + gitweb options
* (eventually) adjust server configuration for CGI in the wanted dir
DONE.
Also, having configuration information spread across several files
(README/INSTALL/gitweb.cgi) doesn't help much.
It is also very strange to have README/"How to configure gitweb for your local
system" saying "You can specify the following configuration variables when
buiding GIT". That means I have to rebuild GIT (actually, only
gitweb/gitweb.cgi) to configure gitweb => I need to download the sources by
hand instead of using the already installed gitweb on my system (the one
which came with the git package).
Is there any strong reason to have configuration at build-time at all? It
would be a lot easier IMO to have it *just* by config files. I'm saying this
because most of the install process is manual anyway (copying/moving files).
Many thanks,
Mircea
--
http://mircea.bardac.net
next reply other threads:[~2007-06-03 5:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 16:53 Mircea Bardac [this message]
2007-06-03 18:36 ` gitweb on shared hosting Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2007-06-03 15:35 Martin Koegler
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=200706021953.09942.dev.list@mircea.bardac.net \
--to=dev.list@mircea.bardac.net \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).