X-Git-Url: http://git.freeside.biz/gitweb/?p=freeside.git;a=blobdiff_plain;f=rt%2FREADME;h=c76045559516cae17bfe1c0dc3ba23eb862e0cac;hp=bdd8e0928d1514a4d8ca86789e13cc6a8e21c08a;hb=01721976fa3324f41a3093cda68bc38a7eec5ff5;hpb=0ed195595b5c7ea404c8848d9d1881ada4214489 diff --git a/rt/README b/rt/README index bdd8e0928..c76045559 100755 --- a/rt/README +++ b/rt/README @@ -27,9 +27,9 @@ o A supported SQL database upgrade path guaranteed o Apache version 1.3.x or 2.x (http://httpd.apache.org) - with mod_perl -- (http://perl.apache.org) - or with FastCGI -- (http://www.fastcgi.com) - or other webserver with FastCGI support + with FastCGI -- (http://www.fastcgi.com) + or mod_perl -- (http://perl.apache.org) + or another webserver with FastCGI support RT's FastCGI handler needs to access RT's configuration file. @@ -67,13 +67,13 @@ GENERAL INSTALLATION If you are upgrading from a previous version of RT, please review the upgrade notes for the appropriate versions, which can be found in docs/UPGRADING-* If you are coming from 4.0.x to 4.2.x you should - review both the UPGRADING-4.0 and UPGRADING-4.2 file. Similarly, if - you were coming from 3.8.x, you would want to review UPGRADING-3.8, - UPGRADING-4.0 and UPGRADING-4.2 + review both the UPGRADING-4.0 and UPGRADING-4.2 files. Similarly, if + you were coming from 3.8.x, you would want to review the UPGRADING-3.8, + UPGRADING-4.0 and UPGRADING-4.2 documents. Any upgrade steps given in version-specific UPGRADING files should be run after the rest of the steps below; however, please read the - relevant documentation before beginning the upgrade, soas to be + relevant documentation before beginning the upgrade, so as to be aware of important changes. RT stores the arguments given to ./configure at the top of the @@ -159,7 +159,7 @@ GENERAL INSTALLATION You should back up your database before running this command. When you run it, you will be prompted for your previous version of - RT (such as 3.8.1) so that the appropriate set of database + RT (such as 4.0.23) so that the appropriate set of database upgrades can be applied. If 'make upgrade-database' completes without error, your upgrade @@ -216,6 +216,9 @@ GENERAL INSTALLATION perldoc /opt/rt4/bin/rt-mailgate +11) Set up automatic backups for RT and its data as described in + the docs/backups.pod document. + GETTING HELP ------------ @@ -230,25 +233,20 @@ more information about commercial support options, please send email to to discuss rates and availability. -MAILING LISTS AND WIKI ----------------------- +COMMUNITY FORUM AND WIKI +------------------------ To keep up to date on the latest RT tips, techniques and extensions, you -may wish to join the rt-users mailing list. Send a message to: - - rt-users-request@lists.bestpractical.com - -with the body of the message consisting of only the word: +may wish to join the RT Community Forum website. You can find it here: - subscribe + https://forum.bestpractical.com -If you're interested in hacking on RT, you'll want to subscribe to -. Subscribe to it with instructions -similar to those above. Address questions about the stable release to -the rt-users list, and questions about the development version to the -rt-devel list. +You'll find many different categories of discussion there including the +RT Users category for general RT topics. If you're interested +in customizing RT code, there is a category for RT Developers with more +technical topics. -The RT wiki, at http://requesttracker.wikia.com/ , is also a potential +The RT wiki, at https://rt-wiki.bestpractical.com, is also a potential resource. @@ -259,7 +257,7 @@ If you believe you've discovered a security issue in RT, please send an email to with a detailed description of the issue, and a secure means to respond to you (such as your PGP public key). You can find our PGP key and fingerprint at -http://bestpractical.com/security/ +https://bestpractical.com/security/ BUGS @@ -267,7 +265,7 @@ BUGS RT's a pretty complex application, and as you get up to speed, you might run into some trouble. Generally, it's best to ask about things you run -into on the rt-users mailinglist (or pick up a commercial support +into on the Community Forum (or pick up a commercial support contract from Best Practical). But, sometimes people do run into bugs. In the exceedingly unlikely event that you hit a bug in RT, please report it! We'd love to hear about problems you have with RT, so we can @@ -278,7 +276,7 @@ fix them. To report a bug, send email to . # # COPYRIGHT: # -# This software is Copyright (c) 1996-2015 Best Practical Solutions, LLC +# This software is Copyright (c) 1996-2017 Best Practical Solutions, LLC # # # (Except where explicitly superseded by other copyright notices)