Installation confusion with rt-1-3-49_01


#1

And now a couple more things about the README, Makefile and config.pm

I like the testdeps program. :slight_smile:

Nothing strange in the Makfile, but some of it could have been
configured automaticly.

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.”

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.

$Timezone : Some reference to a list of timezones would have helped.
I found help by “apropos timezone”.

$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.)

$WebrtImagePath : Now I couldn’t find any information on where to
point this URL. It doesn’t seem to be used.

$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…

$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.

$LocalePath : I don’t know what to do here. What is po files? How do
I create them?

$TicketBaseURI : What is this?

THE WEB UI

I choosed to make /tools/rt2 a softlink to /usr/local/rt2/WebRT/html

And I inserted a .htaccess in that directory with the content:

SetHandler perl-script
PerlHandler RT::Mason

I could also insert the require line:

PerlRequire /usr/local/rt2/bin/webmux.pl

If I did that, I wouldn’t have to change anything in the global apache
configuration. But the application would be much slover because the
initialization will happen on request insted of before the request.

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.

jonas@rit.se RIT AB http://www.rit.se
Box 70, 428 21 Kållered Besök: G:a Riksvägen 36
Tel: +46 (0)31 751 8600 Fax: +46 (0)31 751 8609


#2

And now a couple more things about the README, Makefile and config.pm

I like the testdeps program. :slight_smile:

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@eruditorum.orgjesse@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.


#3

Jesse jesse@fsck.com writes:

Nothing strange in the Makfile, but some of it could have been
configured automaticly.

like what?

Like the database server choosen in the testdep step.

$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.

Maby it was. The makefile doen’t let me do a make without an install,
so I cant test it agian.

But it didn’t explicitly say that the value shouldn’t be changed. I
guess I should have known that.

$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.

I nice feature. :slight_smile:

$TicketBaseURI : What is this?

it’s for the linking interface. you shouldn’t need to touch it.

Ah. It’s an URI. :slight_smile:

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

I know my Apache pretty well. It’s no problem if you configured the
access rights for it.

But there was another problem! The web user (www-data) couldn’t read
the config moudule:

-r-x------ 1 root rt 9122 mar 9 15:32 config.pm

It should be protected, since it has a password for the database.
But www-data can’t read it.

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.

It’s no problem at all. It’s nice to have the configuration collected
in one place, and keep the main apache configuration clean. And I
don’t think it affects performance either.

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 found the bug database. It helped med to understand the usage a
bit. :slight_smile:

jonas@rit.se RIT AB http://www.rit.se
Box 70, 428 21 Kållered Besök: G:a Riksvägen 36
Tel: +46 (0)31 751 8600 Fax: +46 (0)31 751 8609


#4

Jesse jesse@fsck.com writes:

Like the database server choosen in the testdep step.

make testdeps and make fixdeps now exist in the makefile. thanks.
and the readme even now tells you to use them :wink:

$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.

Maby it was. The makefile doen’t let me do a make without an install,
so I cant test it agian.

make upgrade

But it didn’t explicitly say that the value shouldn’t be changed. I
guess I should have known that.

I’ve added comments to this effect to config.pm. thanks.

$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.

I nice feature. :slight_smile:

Indeed. It’s definitely something I want to get to, but wasn’t something
that I was able to get to for 2.0.

$TicketBaseURI : What is this?

it’s for the linking interface. you shouldn’t need to touch it.

Ah. It’s an URI. :slight_smile:

Yep.

I know my Apache pretty well. It’s no problem if you configured the
access rights for it.

But there was another problem! The web user (www-data) couldn’t read
the config moudule:
It should be protected, since it has a password for the database.
But www-data can’t read it.

nod That’s one of the things you’ll win with when you put the config
in your main apache httpd.conf. As you’re starting apache as root, you
won’t have to worry about it.

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

“That package looks like what I wanted, but the site was down today,
so I decided to reimplement it in Perl.”
-me


#5

At 9:44 PM +0100 3/9/01, Jonas Liljegren wrote:

And now a couple more things about the README, Makefile and config.pm
[…]

$Timezone : Some reference to a list of timezones would have helped.
I found help by “apropos timezone”.

Seconded.

I’m not really clear on why this is needed, and see possible problems
arising from it. Date::Manip::Date_Init() should be able to figure
out the system’s default zone offset and stash it in Date::Manip::TZ
for use by its routines. Unless there is a need for an RT instance
to have a different default, that should suffice. If it must be
there, some warning is justified, since there’s not a lot of
standardization across OS’s. For example, the distribution has
"US/Eastern" which probably is fine on Linux (and maybe Solaris?) but
isn’t on FreeBSD. That form is usually a pathname relative to the
OS’s root for zoneinfo files, and it seems that every OS uses a
different root, layout, and naming convention for those files.

Bill Cole
Director of Customer Operations, MAPS L.L.C.
wkc@mail-abuse.org (work)
bill@scconsult.com (personal)