3 Detailed information about upgrading can be found in the README file.
4 This document is intended to supplement the instructions in that file.
6 Additional information about upgrading from specific versions of RT is
13 Before making any changes to your database, always ensure that you have a
14 complete current backup. If you don't have a current backup, you could
15 accidentally damage your database and lose data or worse.
19 UPGRADING FROM 3.3.14 and earlier - Changes:
21 The "ModifyObjectCustomFieldValues" right name was too long. It's been changed to
25 UPGRADING FROM 3.3.11 and earlier - Changes:
29 Custom Fields now have an additional right "ModifyCustomField".
30 This right governs whether a user can modify an object's custom field values
31 for a particular custom field. This includes adding, deleting and changing values.
34 UPGRADING FROM 3.2 and earlier - Changes:
38 Now, if you want any user to be able to access the Admin tools (a.k.a.
39 the Configuration tab), you must grant that user the "ShowConfigTab"
40 right. Making the user a privileged user is no longer sufficient.
42 "SuperUser" users are no longer automatically added to the list of users who can own tickets in a queue. You now need to explicitly give them the "own tickets" right.
46 UPGRADING FROM 3.0.x - Changes:
50 We recommend you move your existing /opt/rt3 tree completely out
51 of the way before installating the newversion of RT, to make sure
52 that you don't inadvertently leave old files hanging around.
56 Now, if you want RT to automatically create new users upon ticket
57 submission, you MUST grant 'Everyone' the right to create tickets.
58 Granting this right only to "Unprivileged Users" is now insufficient.
61 = FastCGI configuration =
63 This section is a snapshot of the documentation available at:
65 http://wiki.bestpractical.com/index.cgi?FastCGIConfiguration
67 It's worth checking out that resource if these instructions don't
71 RT 3.2 includes a signficant change to the FastCGI handler. It is
72 no longer "setgid" to the RT group. Perl's setid support has been
73 deprecated for the last several releases and a number of platforms
74 don't bundle the "sperl" or "suidperl" executable by default.
75 Additionally, when perl is run SetUID or SetGID, the interpreter
76 is automatically switched into /taint mode/, in which all incoming
77 data, no matter the source is considered suspect. At first, this
78 seems like a great idea. But perl's taint mode is a big sledgehammer
79 used to hit small nails. Many perl libraries aren't tested in taint
80 mode and will fail when least expected. Moving away from a SetGID
81 FastCGI handler will enable more users to have a smoother RT
82 experience. It does require some changes in how you set up and
85 Beginning with RT 3.2, you have several choices about how to configure
86 RT to run as a FastCGI:
89 == Install RT as the user your webserver runs as ==
91 Pros: Very easy to configure
93 Cons: Your webserver has access to RT's private database password
98 When installing RT, run:
100 ./configure --with-web-user="webuser" --with-web-group="webgroup" \
101 --with-rt-user="webuser" --with-rt-group="webgroup"
103 (Don't forget to include other configuration options that matter to you)
105 If you're using apache, you'll want to add something like the following
108 <VirtualHost rt.example.com>
110 # Pass through requests to display images
111 Alias /NoAuth/images/ /opt/rt3/share/html/NoAuth/images/
113 # Tell FastCGI to put its temporary files somewhere sane.
116 FastCgiServer /opt/rt3/bin/mason_handler.fcgi -idle-timeout 120
118 AddHandler fastcgi-script fcgi
119 ScriptAlias / /opt/rt3/bin/mason_handler.fcgi/
124 == Make your webserver user a member of the "rt" group ==
126 Pros: Easy to configure
128 Cons: Your webserver has access to RT's private database password
133 Install RT normally. Add whichever user your webserver runs as
134 (whatever you set --with-web-user to) to the "rt" group (whatever
135 you set --with-rt-group to) in /etc/groups.
137 To find out what user your webserver runs as, look for the line
141 in your apache httpd.conf. Common values are www, www-data, web and nobody.
145 == Run RT using _suexec_ or a similar mechanism
150 Cons: Sometimes very difficult to configure
152 Apache's _suexec_ utility allows you run CGI programs as specific
153 users. Because that's a relatively heavy responsibility, it's very,
154 very conservative about what it's willing to do for you. On top of
155 that, Apache's mod_fastcgi plugin doesn't respect all of suexec's
156 features. While suexec is designed to execute CGI scripts in a
157 given virtual host's !DocumentRoot, It can only execute FastCGI
158 scripts in the system's *main* !DocumentRoot.
160 This means you have to copy the RT FastCGI handler into your main
163 The following example !VirtualHost will run RT as a FastCGI on
164 Apache 1.3 on a Debian Linux server.
167 <VirtualHost rt.example.com>
169 DocumentRoot /opt/rt3/share/html
171 # Set the rt user and group as the executing user for this virtual host
176 # Pass through requests to display images
177 Alias /NoAuth/images/ /opt/rt3/share/html/NoAuth/images/
179 # Tell FastCGI to put its temporary files somewhere sane.
182 # Tell FastCGI that it should use apache's "suexec" binary to call any
184 # This is a GLOBAL setting
185 FastCgiWrapper /usr/lib/apache/suexec
187 # You need to copy the rt mason_handler.fcgi into a directory inside
188 # the main server DocumentRoot
189 # That directory must be owned by the user and group that will execute
191 # In this case, that directory is /var/www/rt
193 # To find the local DocumentRoot, run "suexec -V" as root and look for the
194 # -D DOC_ROOT parameter.
196 # Apache 1.3 discards the user and group parameters on the FastCgiServer
197 # line. Apache 2.0 requires them.
199 FastCgiServer /var/www/rt/mason_handler.fcgi -idle-timeout 120 -user rt -group rt
201 AddHandler fastcgi-script fcgi
202 ScriptAlias / /var/www/rt/mason_handler.fcgi/