From: cgit at cryptocrack.de (Lukas Fleischer)
Subject: REQUEST: better install support/documentation
Date: Wed, 31 Aug 2011 11:14:51 +0200 [thread overview]
Message-ID: <20110831091451.GB5101@blizzard> (raw)
In-Reply-To: <CA+L2dvEGRLKe=qoimEgSEhmV7k_jQfMoGkqRP4aNJUhc=xnmPw@mail.gmail.com>
On Tue, Aug 30, 2011 at 03:10:14PM -0400, Ryan Lewis wrote:
> Hi,
>
> I very much want to use your software, but, I have too much trouble
> installing it.
>
> the purpose of a Makefile is to alleviate the stress of configuration,
> if there needs to be an appropriate .htaccess file generated, can you
> please automate this, instead of vaguely instructing us what needs to
> be done in a README, or at least, be a bit more detailed about what
> needs to be done.
-1 to creating a ".htaccess" file automatically. The configuration
changes needed heavily depend on the type of web server that is used and
the general setup. We should not make assumptions. A good administrator
should know what to do.
Agreed that documentation isn't perfect. Feel free to submit a patch.
>
> Also, the install process assumes root and installation in some root
> directory, most people hosting websites use shared hosts, without root
> access. can you make it so that I can point the makefile at a
> directory (like the directory where files for git.foobar.com) and
> maybe a /home/cgit directory, where any configuration files or
> repositories might live?
Use "DESTDIR" to specify any non-standard root directory (this is pretty
standard). Use "CGIT_SCRIPT_PATH" to specify an alternate patch to put
the CGI files into.
$ make CGIT_SCRIPT_PATH=/bar DESTDIR=/foo install
... to install them to "/foo/bar", for example.
>
> since you clearly seem to know how to set this up, it would be nice if
> you could give us, those who want to use your software, some help.
>
> thanks for all your help, and I really like CGIT,
>
> -rhl
>
> _______________________________________________
> cgit mailing list
> cgit at hjemli.net
> http://hjemli.net/mailman/listinfo/cgit
next prev parent reply other threads:[~2011-08-31 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 19:10 me
2011-08-31 9:14 ` cgit [this message]
2011-09-01 16:51 ` me
2011-09-02 9:04 ` cgit
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=20110831091451.GB5101@blizzard \
--to=cgit@lists.zx2c4.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 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).