A PCRE internal error occured. This might be caused by a faulty plugin
Changes RSS

====== Differences ====== This shows you the differences between two versions of the page.

Link to this comparison view

guides:rt3.8 [2009/03/05 00:38]
fishy
guides:rt3.8 [2009/03/16 16:02] (current)
fishy
Line 1: Line 1:
-http://wiki.bestpractical.com/view/DebianLennyInstallGuide+====== How I installed Request Tracker 3.8.2 on Debian Lenny ====== 
 + 
 +My first hints and pointers were from the poorly formatted guide at: 
 + 
 +  * http://wiki.bestpractical.com/view/DebianLennyInstallGuide 
 + 
 +===== Basic prerequisites =====
  
 Install "providing" software. By this, I mean software that is needed to compile software, serve data to the web, test the data served, and communicate with the world.  Install "providing" software. By this, I mean software that is needed to compile software, serve data to the web, test the data served, and communicate with the world. 
 +
 <code> <code>
 apt-get install build-essential bzip2 \ apt-get install build-essential bzip2 \
Line 24: Line 31:
 sudo apt-get install postfix sudo apt-get install postfix
 </code> </code>
 +
 +
 +===== Perl prerequisites... =====
  
 Next up is a shockingly long list of development- and perl-dependencies. The commands below are split into chunks that the BASH shell will accept, but the order, and eventual dependency satification is not taken into consideration. I.e. the list is for completeness. Next up is a shockingly long list of development- and perl-dependencies. The commands below are split into chunks that the BASH shell will accept, but the order, and eventual dependency satification is not taken into consideration. I.e. the list is for completeness.
 +
 Your mileage may vary on what you actually need to install. Your mileage may vary on what you actually need to install.
 +
 +==== OS packaged perl-dependencies ====
  
 <code> <code>
Line 59: Line 72:
                 libxml-namespacesupport-perl                 libxml-namespacesupport-perl
 </code> </code>
 +
 +==== CPAN setup ====
  
 Now, prepare your Perl CPAN setup, as Request Tracker installation __will__ use CPAN to pull in even more dependencies! Now, prepare your Perl CPAN setup, as Request Tracker installation __will__ use CPAN to pull in even more dependencies!
 Here follows a somewhat complete(ish) summary of my interaction with CPAN: Here follows a somewhat complete(ish) summary of my interaction with CPAN:
-<code> +[[guides:rt3.8:CPAN]]
-sudo perl -MCPAN -e shell +
-Would you like me to configure as much as possible automatically? [yes] no +
-CPAN build and cache directory? [/home/username/.cpan] +
-Download target directory? [/home/fishy/.cpan/sources] +
-Directory where the build process takes place? [/home/fishy/.cpan/build] +
-CPAN.pm sessions? [yes] +
-building modules that need some customization? [/home/fishy/.cpan/prefs] +
-Always commit changes to config variables to disk? [no] +
-Cache size for build directory (in MB)? [100] +
-Let the index expire after how many days? [1] +
-Perform cache scanning (atstart or never)? [atstart] +
-Cache metadata (yes/no)? [yes] +
-Use CPAN::SQLite if available? (yes/no)? [no] yes +
-Policy on building prerequisites (follow, ask or ignore)? [ask] follow +
-Policy on installing 'build_requires' modules (yes, no, ask/yes, +
-ask/no)? [ask/yes] yes +
-Always try to check and verify signatures if a SIGNATURE file is in +
-the package and Module::Signature is installed (yes/no)? [no] +
-Email test reports if CPAN::Reporter is installed (yes/no)? [no] +
-Do you want to enable code deserialisation (yes/no)? [noyes +
-Where is your bzip2 program? [/bin/bzip2] +
-Where is your gzip program? [/bin/gzip] +
-Where is your tar program? [/bin/tar] +
-Where is your unzip program? [/usr/bin/unzip] +
-Where is your make program? [/usr/bin/make] +
-Where is your curl program? [/usr/bin/curl]  +
-Where is your lynx program? [/usr/bin/lynx]  +
-Where is your ncftpget program? [] +
-Where is your ncftp program? [] +
-Where is your ftp program? [/usr/bin/ftp] +
-Where is your gpg program? [/usr/bin/gpg] +
-Where is your patch program? [/usr/bin/patch] +
-Where is your applypatch program? [/usr/bin/applypatch]  +
-What is your favorite pager program? [/usr/bin/less] +
-What is your favorite shell? [/bin/bash] +
-Tar command verbosity level (none or v or vv)? [v] +
-Verbosity level for loading modules (none or v)? [v] +
-Do you want to turn this message off? [no] +
-In case you can choose between running a Makefile.PL or a Build.PL, +
-which installer would you prefer (EUMM or MB or RAND)? [MB] +
-Parameters for the 'perl Makefile.PL' command? [INSTALLDIRS=site] +
-Parameters for the 'make' command? Typical frequently used setting: +
- +
-    -j3              # dual processor system (on GNU make)+
  
- &lt;make_arg> +===== Download &ampunpack Request Tracker =====
-Your choice: []+
  
-Do you want to use a different make command for 'make install'? 
-Cautious people will probably prefer: 
- 
-    su root -c make 
- or 
-    sudo make 
- or 
-    /path1/to/sudo -u admin_account /path2/to/make 
- 
- <make_install_make_command> 
-or some such. Your choice: [/usr/bin/make] 
-^[[5~ 
-Parameters for the 'make install' command? 
-Typical frequently used setting: 
- 
-    UNINST=1         # to always uninstall potentially conflicting files 
- 
- <make_install_arg> 
-Your choice: [] UNINST=1 
- 
-A Build.PL is run by perl in a separate process. Likewise we run 
-'./Build' and './Build install' in separate processes. If you have any 
-parameters you want to pass to the calls, please specify them here. 
- 
-Typical frequently used settings: 
- 
-    --install_base /home/xxx             # different installation directory 
- 
- <mbuildpl_arg> 
-Parameters for the 'perl Build.PL' command? [] 
- 
-Parameters for the './Build' command? Setting might be: 
- 
-    --extra_linker_flags -L/usr/foo/lib  # non-standard library location 
- 
- <mbuild_arg> 
-Your choice: [] 
- 
-Do you want to use a different command for './Build install'? Sudo 
-users will probably prefer: 
- 
-    su root -c ./Build 
- or 
-    sudo ./Build 
- or 
-    /path1/to/sudo -u admin_account ./Build 
- 
- <mbuild_install_build_command> 
-or some such. Your choice: [./Build] 
- 
-Parameters for the './Build install' command? Typical frequently used 
-setting: 
- 
-    --uninst 1                           # uninstall conflicting files 
- 
- <mbuild_install_arg> 
-Your choice: [] --uninst 1 
- 
-Timeout for inactivity during {Makefile,Build}.PL? [0] 
-Your ftp_proxy? [] 
-Your http_proxy? [] 
-Your no_proxy? [] 
-Shall we always set the FTP_PASSIVE environment variable when dealing 
-with ftp download (yes/no)? [yes] 
-Preferred method for determining the current working directory? [cwd] 
-Do you want the command number in the prompt (yes/no)? [yes] 
-Do you want to turn ornaments on? [yes] 
-Do you want to turn on colored output? [no] 
-Your terminal expects ISO-8859-1 (yes/no)? [yes] 
-File to save your history? [/home/fishy/.cpan/histfile] 
-Number of lines to save? [100] 
-Always try to show upload date with 'd' and 'm' command (yes/no)? [no] 
-Show all individual modules that have no $VERSION? [no] 
-Show all individual modules that have a $VERSION of zero? [no] 
-Is it OK to try to connect to the Internet? [yes] 
-Select your continent (or several nearby continents) [] 4 
-Select your country (or several nearby countries) [] 19 
- e.g. '1 4 5' or '7 1-4 8' [] 2 
-Enter another URL or RETURN to quit: [] 
- 
-cpan[2]> install Bundle::CPAN 
-cpan[2]> install CPAN::SQLite  
- 
-</code> 
  
 Now, download and unpack Request Tracker, the latest release: Now, download and unpack Request Tracker, the latest release:
Line 203: Line 89:
 cd rt-3.* cd rt-3.*
 </code> </code>
 +
 +===== Setting up the source tree =====
 +
 +The following code sets up my RT install to dump the instance files into the dir /opt/rt/defcon, and
 +use MySQL for storage
  
 <code> <code>
Line 242: Line 133:
 </code> </code>
  
-This uses CPAN to pull in the missing or out-dated Perl modules.+This uses CPAN to pull in the missing or out-dated Perl modules. After a successful run, rerun make testdeps, and you shuld get: 
 +<code> 
 +All dependencies have been found. 
 +</code> 
 + 
 +===== Installation ===== 
 + 
 +Time to do the actual installation: 
 +<code> 
 +sudo make install 
 + 
 +... 
 +</code> 
 + 
 +===== Configuration of RT ===== 
 + 
 +You must now configure RT by editing /opt/rt/defcon/etc/RT_SiteConfig.pm.  
 + 
 +WARNING: Never, EVER, change RT_Config.pm. All your changes need to be put in 
 +RT_SiteConfig.pm. 
 + 
 +(You will definitely need to set RT's database password in  
 +/opt/rt/defcon/etc/RT_SiteConfig.pm before continuing. Not doing so could be  
 +very dangerous.  Note that you do not have to manually add a  
 +database user or set up a database for RT.  These actions will be  
 +taken care of in the next step.) 
 + 
 +So, the natural next step is to open $PREFIX/etc/RT_SiteConfig.pm in your favourite text-editor, and decide on the basic setting of this instance... 
 + 
 +<code> 
 + 
 +# What RT instance? 
 +Set($rtname, 'Ticket'); 
 +Set($Organization , "defcon.no"); 
 + 
 +# Default email adresses 
 +Set($CorrespondAddress , 'rt@defcon.no'); 
 +Set($CommentAddress , 'rt-comment@defcon.no'); 
 + 
 +# How to handle time (timezone setting) 
 +Set($Timezone , 'CET'); 
 + 
 +# Database setup 
 +#Set($DatabaseHost   , 'localhost'); 
 +#Set($DatabaseRTHost , 'localhost'); 
 +#Set($DatabasePort , ''); 
 +Set($DatabaseType, 'mysql'); 
 +Set($DatabaseUser , 'rt_user'); 
 +Set($DatabasePassword , 'password'); 
 +Set($DatabaseName , 'rt_database'); 
 + 
 +# Who is owner/admin of this instance? 
 +Set($OwnerEmail , 'rtowner@defcon.no'); 
 +Set($LoopsToRTOwner , 1); 
 + 
 +# Max allowed attachments, up from 10MB to 20MB 
 +Set($MaxAttachmentSize , 20000000); 
 + 
 +# Where do we exist on the web? 
 +Set($WebDomain, 'rt.home.defcon.no'); 
 + 
 +# RT resides on the root of the previous name... 
 +Set($WebPath, ""); 
 + 
 +</code> 
 + 
 +===== Initialize the RT database ===== 
 + 
 +<code> 
 +sudo make initialize-database 
 +</code> 
 + 
 +===== Configure HTTPd ===== 
 + 
 +I am using Apache2, and running RT through mod_perl. Note the PerlRequire, SetHandler and PerlResponseHandler. Without these, your RT will __not__ work. 
 + 
 +<code> 
 +# /etc/apache2/sites-available/rt.home.defcon.no 
 +<VirtualHost *:80> 
 + 
 +ServerName rt.home.defcon.no 
 + 
 +DocumentRoot /opt/rt/defcon/share/html 
 +PerlRequire "/opt/rt/defcon/bin/webmux.pl" 
 + 
 +<Location /> 
 +    AddDefaultCharset UTF-8 
 +    SetHandler perl-script 
 +    PerlResponseHandler RT::Mason 
 +</Location> 
 + 
 +</VirtualHost>  
 + 
 +</code> 
 + 
 +As this is a Debian Lenny system, I used the Debian helper tools to enable all needed apache2 related configurations: 
 + 
 +<code> 
 +sudo /usr/sbin/a2enmod perl 
 +sudo /usr/sbin/a2enmod rewrite 
 +sudo /usr/sbin/a2ensite rt.home.defcon.no 
 +sudo /etc/init.d/apache2 reload 
 +</code> 
 + 
 +===== First look at the installed RT ===== 
 + 
 +Go to the address you have configured in Apache, DNS and RT_SiteConfig.pm, and you should be greeted with the login-box of RT3.8! 
 + 
 +Log in as "root" with password "password". Now SET A NEW PASSWORD ! (!) 
 +  * Preferences 
 +    * About me 
 +    * Password 
 +      * New passord 
 +      * Retype passord 
 + 
 +===== Post install setup ===== 
 + 
 +That's not all, but it is all for now... 
 + 
 +==== Overriding the footer ==== 
 + 
 +<code> 
 +web:/opt/rt/defcon# mkdir local/html/Elements 
 +web:/opt/rt/defcon# cp share/html/Elements/Footer local/html/Elements/ 
 +web:/opt/rt/defcon# vim local/html/Elements/Footer  
 +</code> 
 + 
 +==== Setting up default permissions ==== 
 + 
 +==== Adding a few queues ====