[rt-users] RT installation - theoretical installer

[Stuart Browne]

It would be possible to have your own perl installed into its own structure, with all its own localized modules, with its own library path pointing to where it was installed.

What would be difficult with a canned install however would be the web server configuration required / mod_perl stuff.

From: rt-users-bounces at lists.bestpractical.com [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Joseph Spenner
Sent: Tuesday, 23 December 2008 05:58
To: rt-users at lists.bestpractical.com
Subject: [rt-users] RT installation - theoretical installer

Would it be possible to have a totally canned RT, perhaps with its own perl with all the modules needed, and installed via some sort of web based installer?  Consider the following scenario:   I have a web/domain provider who handles my storage needs, such as godaddy.com.  I have tons of web space, but no control over the perl modules.  However, if everything were installed in my web space such that the canned RT cgi knew where to find its own perl, everything should work.  I can create aliases to point to queues as well, via my web providers' control panel tools.

A similar type of installer exists for a wonderful piece of free forums software called SMF ( http://www.simplemachines.org/ ).  It has a couple initial manual steps:  create a database on some mysql/postgress system, create a database user with admin rights on that database.   That info is then entered that into a field of the web installer along with the location of the database, and hit GO.  It builds everything, lets you configure everything via a web interface, etc.

Perhaps I'm over simplifying the installation, so please feel free to point out the flaws.  The idea just popped into my head as I was taking a walk, spacing off.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20081223/484af72f/attachment.htm>