[aklug] Re: Apache2 and Perl

I looked into that and decided not to go that rout. I'm sure it works
but I would like a little extra control. In this case I have to hope
the Turnkey team updates things on a regular bases.
There's also issues with added software. If I want to run something else
will it allow me to do that. Too much to figure out.

Not sure I can manage the system I'm trying to build but it gives me options.
I won't know until I finish installing and testing the
system.

Sent from my iPhone

On Dec 27, 2011, at 6:37 PM, Dan Wolf <dan-wolf@gci.net> wrote:

Not sure if this will help or not , but I have found 'Turnkey' can save you
a considerable amount of time getting an appliance system up, such as OTRS -
Open Ticket Request System. This setup includes the entire infrastructure
plus some nice add-ons...... here - http://www.turnkeylinux.org/otrs .
Additionally they have a variety of appliances which are available as
standalone, VM's, or cloud based.

-----Original Message-----
From: aklug-bounce@aklug.org [mailto:aklug-bounce@aklug.org] On Behalf Of
Damien Hull
Sent: Tuesday, December 27, 2011 4:28 PM
To: Michael Fowler
Cc: aklug@aklug.org
Subject: [aklug] Re: Apache2 and Perl

Thanks for the info. I'll post something as soon as I have it working.
Or as soon as I brake something...

On Dec 27, 2011, at 4:24 PM, Michael Fowler <michael@shoebox.net> wrote:

On Tue, Dec 27, 2011 at 04:02:01PM -0900, Damien Hull wrote:

I'm trying to install Request Tracker. It seems I missed some of the

documentation. Turns out they want people to use Starman to run the

application. Apache is only there as a proxy.

I guess that's what you are talking about. I have most of it

installed. I just need to figure out how to start the app with

Starman and get apache mod_proxy working.

Ah, so you're using the application server method. The most direct

instructions I can find for getting things configured are directly out

of the docs directory:

https://github.com/bestpractical/rt/blob/stable/docs/web_deployment.po

d

The Starman instructions are in the 'Standalone' section. Once you've

started it you get a standalone web server; making sure it's kept

running across reboots and crashes is then up to you, probably through

cron jobs and an init script.

To proxy it you'll need to load mod_proxy by symlinking the

configuration:

  cd /etc/apache2/mods-enabled

  ln -s ../mods-available/proxy.conf

  ln -s ../mods-available/proxy.load

There's probably a script installed somewhere that will do this for you.

From there it's a matter of configuring your proxying; the simplest

would be to add a ProxyPass directive in the relevant VirtualHost

section:

  ProxyPass /rt http://localhost:8080

This opens the application server directly to external access;

assuming you trust the security, it should be fine; make sure to run

it under as limited a user as possible. FastCGI would be a little

more protected; then you'd be dealing with just the security problems of

RT itself.

That should do it, let us know if it works.

--
Michael Fowler
www.shoebox.net
---------
To unsubscribe, send email to <aklug-request@aklug.org> with
'unsubscribe' in the message body.
---------
To unsubscribe, send email to <aklug-request@aklug.org> with 'unsubscribe'
in the message body.
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.