[rt-devel] Installation confusion with rt-1-3-49_01
Jesse
jesse at fsck.com
Fri Mar 9 16:38:00 EST 2001
On Fri, Mar 09, 2001 at 09:44:58PM +0100, Jonas Liljegren wrote:
> And now a couple more things about the README, Makefile and config.pm
>
> I like the testdeps program. :-)
Thanks.
> Nothing strange in the Makfile, but some of it could have been
> configured automaticly.
like what?
> I haven't tried fixing the mail gateways for RT2 yet. There is a note
> about the mail gateway hasn't been implemented yet. Is that true?
> "NOTE: This is not yet implemented for RT2."
That refers only to the command mode. I'll take an axe to the readme
> The config.pm:
>
> $rtname : I didn't know that the web UI was going to display the name
> as RT/$rtname. My first choice was RT, which gave me RT/RT.
meri is working on docs for config.pm... which, iirc, explain more fully
that $rtname should almost always be your domain.
> $Timezone : Some reference to a list of timezones would have helped.
> I found help by "apropos timezone".
Well, it varies from OS to OS, but I'll put in something about it being
a timezone as defined by your local OS
> $SendmailArguments : Those agruments didn't work with exim in the old
> RT. But the corresponding "-oi -t -odb -oem" works. (But I think that
> -odb and -oem is the default anyway.)
*nod* which is why it should say that if you're not running sendmail,
you should use '-oi -t'...in fact it does.
> $WebrtImagePath : Now I couldn't find any information on where to
> point this URL. It doesn't seem to be used.
it's now gone. thanks.
>
> $WebPath : This produced many errors for me. I looked at $WebBaseURL
> and found a '/' at the end of the string. This made me conclude that
> $WebPath shouldn't have a '/' at the beginning. The $WebURL variable
> futher showed that neither should it have a slash at the end. I
> configured the variable to:
>
> $WebPath = "tools/rt2";
>
> But that was wrong...
I'll see what I can dig up for better docs for this.
> $MasonComponentRoot : As a person new to Mason, I didn't knew where
> this component root was located. I later found it to be the same as
> the "document root" for rt2. In my case, "/var/www/tools/rt2". (More
> on that later.) Som explanation would have helped.
It's automatically configured by the makefile. you shouldn't have
had to touch it.
> $LocalePath : I don't know what to do here. What is po files? How do
> I create them?
Ignore it. it's for a unimplemented feature.
> $TicketBaseURI : What is this?
it's for the linking interface. you shouldn't need to touch it.
> THE WEB UI
> ----------
>
> I choosed to make /tools/rt2 a softlink to /usr/local/rt2/WebRT/html
be careful. apache can get annoyed at softlinks
> And I inserted a .htaccess in that directory with the content:
>
> SetHandler perl-script
> PerlHandler RT::Mason
um. I've not played with this. if it works for you great. but it's not
the supported setup mechanism.
> I will probla have a ton of questions about the UI and functionality.
> But as a start, I would like to know if there is any documentation. I
> can't figure aout the purpouse and usage of keywords.
there isn't much in the way of docs yet. they're starting to come together
though. I wrote a bit about Scrips the other day that I need to polish and
release. then I wanna do a first pass at ACL docs. and after that, I'll
try to doc keywords, if meri or someone else doesn't beat me to it.
-j
--
jesse reed vincent -- root at eruditorum.org -- jesse at fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90
Linux is like a Vorlon. It is incredibly powerful, gives terse,
cryptic answers and has a lot of things going on in the background.
More information about the Rt-devel
mailing list