ManualInstallation - Revision history

Jbrandt at 16:13, 20 December 2022

2022-12-20T16:13:36Z

← Older revision		Revision as of 12:13, 20 December 2022
Line 320:		Line 320:
	# The configuration varies by database type.		# The configuration varies by database type.
	);</pre>		);</pre>
	Copy the output generated when you run <code>rt-setup-fulltext-index</code> and save it to the file <code>/opt/rt5/etc/RT_SiteConfig~~.d/FulltextIndex~~.pm</code>.		Copy the output generated when you run <code>rt-setup-fulltext-index</code> and save it to the file <code>/opt/rt5/etc/RT_SiteConfig.pm</code>.

	=== Set permissions ===		=== Set permissions ===
Line 328:		Line 328:
	<pre>cd rt-5.0.3		<pre>cd rt-5.0.3
	sudo make fixperms</pre>		sudo make fixperms</pre>

			This is done as part of the installation, so permissions should be correct, but this is helpful if you change something.

	=== Verify the installation ===		=== Verify the installation ===

Line 333:		Line 336:

	<pre>sudo /opt/rt5/sbin/rt-passwd root</pre>		<pre>sudo /opt/rt5/sbin/rt-passwd root</pre>

	Set the password when prompted. Record this; you’ll need it later.		Set the password when prompted. Record this; you’ll need it later.

	== Set up RT’s web server ==		== Set up RT’s web server ==

	Fully documenting how to set up a web server configured for your network with ~~encryption~~ is outside the scope of this guide. This page only highlights the configuration you need to pass web requests onto RT using Apache with mod_fcgid or nginx and the RT FastCGI service.		Fully documenting how to set up a web server configured for your network, with SSL, is outside the scope of this guide. This page only highlights the configuration you need to pass web requests onto RT using Apache with mod_fcgid or nginx and the RT FastCGI service.

	See the [https://docs.bestpractical.com/rt/latest/web_deployment.html RT deployment guide] for the latest recommendations from Best Practical on how to deploy RT.		See the [https://docs.bestpractical.com/rt/latest/web_deployment.html RT deployment guide] for the latest recommendations from Best Practical on how to deploy RT.
Line 553:		Line 557:
	=== Sending Mail ===		=== Sending Mail ===

	RT only knows how to send mail by passing it off to another program on the system. It ~~cannot~~ connect or authenticate directly to external mail servers. In the default configuration, RT runs the standard <code>sendmail</code> command. There are [https://docs.bestpractical.com/rt/latest/RT_Config.html#Outgoing-mail configuration options to send mail through different commands] if you need.		RT only knows how to send mail by passing it off to another program on the system. It does not connect or authenticate directly to external mail servers. In the default configuration, RT runs the standard <code>sendmail</code> command, which is provided by whichever MTA you have installed (postfix, sendmail, exim, qmail, etc.). There are [https://docs.bestpractical.com/rt/latest/RT_Config.html#Outgoing-mail configuration options to send mail through different commands] if you need.

	The most common setup is to install and configure a proper Mail Transfer Agent (MTA) like Postfix or Exim, and then configure it to send mail to the wider Internet as you need. This works well because the MTAs are robust and well-tested; they have flexible configuration to let you send mail out by relaying to other mail servers you specify with optional authentication; and most distributions install one by default anyway. The only hard part is configuring the MTA to send mail following your site’s policies.		The most common setup is to install and configure a proper Mail Transfer Agent (MTA) like Postfix or Exim, and then configure it to send mail to the wider Internet as you need. This works well because the MTAs are robust and well-tested; they have flexible configuration to let you send mail out by relaying to other mail servers you specify with optional authentication; and most distributions install one by default anyway. The only hard part is configuring the MTA to send mail following your site’s policies.
Line 567:		Line 571:
	<pre>rt: "\|/opt/rt5/bin/rt-mailgate --queue general --action correspond --url https://rt.yourdomain.example.com/"		<pre>rt: "\|/opt/rt5/bin/rt-mailgate --queue general --action correspond --url https://rt.yourdomain.example.com/"
	rt-comment: "\|/opt/rt5/bin/rt-mailgate --queue general --action comment --url https://rt.yourdomain.example.com/"</pre>		rt-comment: "\|/opt/rt5/bin/rt-mailgate --queue general --action comment --url https://rt.yourdomain.example.com/"</pre>

	This works well because, again, you’re probably running an MTA anyway; and the MTA can hold and queue mail if it comes in while RT is down for any reason, giving you a buffer against downtime.		This works well because, again, you’re probably running an MTA anyway; and the MTA can hold and queue mail if it comes in while RT is down for any reason, giving you a buffer against downtime.

Jbrandt at 14:55, 20 December 2022

2022-12-20T14:55:31Z

← Older revision		Revision as of 10:55, 20 December 2022
Line 154:		Line 154:
	Creating separate RT system accounts is optional. Running configure will usually auto detect the correct group and user to use for setting permissions. See the [https://docs.bestpractical.com/rt/latest/configure.html group and user related options for configure] to fine tune the permissions.		Creating separate RT system accounts is optional. Running configure will usually auto detect the correct group and user to use for setting permissions. See the [https://docs.bestpractical.com/rt/latest/configure.html group and user related options for configure] to fine tune the permissions.

	This account will be used throughout the install process to control access to sensitive files. Run:		You can create this user and group if you prefer not to install as root. This account will be used throughout the install process to control access to sensitive files. Run:

	<pre>sudo groupadd --system rt		<pre>sudo groupadd --system rt
Line 169:		Line 169:
	=== Pre-configure RT ===		=== Pre-configure RT ===

	~~This~~ command will detect some information about your system in order to install RT properly, and decide which set of dependencies to install. Here’s what the different parts of our command are doing:		The [https://docs.bestpractical.com/rt/latest/configure.html configure] command will detect some information about your system in order to install RT properly, and decide which set of dependencies to install. Here’s what the different parts of our command are doing:

	* <code>PERL=…</code> configures RT to run under Perl with some options that load its dependencies from a dedicated directory. The <code>/opt/rt5</code> part of this string should match your <code>prefix</code> setting (see next item). If you know you want to use a specific Perl installed on your system, you can specify its full path instead of the plain <code>perl</code> here.		* <code>PERL=…</code> configures RT to run under Perl with some options that load its dependencies from a dedicated directory. The <code>/opt/rt5</code> part of this string should match your <code>prefix</code> setting (see next item). If you know you want to use a specific Perl installed on your system, you can specify its full path instead of the plain <code>perl</code> here.
Line 177:		Line 177:
	* The rest of the options tell RT to install additional dependencies for optional features.		* The rest of the options tell RT to install additional dependencies for optional features.

	Make sure you have <code>cd</code>ed into the RT source directory, ~~and~~ run:		Make sure you have <code>cd</code>ed into the RT source directory. As an example of manually setting serveral options, you can run:

	<pre>PERL="/usr/bin/env -S perl -I/opt/rt5/local/lib/perl5" ./configure --prefix=/opt/rt5 --with-db-type=TYPE --with-web-user=rt --with-web-group=rt --with-attachment-store=disk --enable-externalauth --enable-gd --enable-graphviz --enable-gpg --enable-smime</pre>		<pre>PERL="/usr/bin/env -S perl -I/opt/rt5/local/lib/perl5" ./configure --prefix=/opt/rt5 --with-db-type=TYPE --with-web-user=rt --with-web-group=rt --with-attachment-store=disk --enable-externalauth --enable-gd --enable-graphviz --enable-gpg --enable-smime</pre>

			Many of the values have default settings, like /opt/rt5 as the prefix. And the configure script will try to find things like the configured <code>perl</code>, so this can also work for a fairly typical RT:

			<pre>./configure --enable-gd --enable-graphviz</pre>

	For more background, [https://docs.bestpractical.com/rt/latest/configure.html refer to the RT configure options documentation].		For more background, [https://docs.bestpractical.com/rt/latest/configure.html refer to the RT configure options documentation].

	=== Install RT and its Perl dependencies ===		=== Install RT and its Perl dependencies ===

	This command will download, build, and install all of the Perl modules necessary to run RT with the configuration you set above. Here’s what the different parts of the command are doing:		This command will download, build, and install all of the Perl modules necessary to run RT with the configuration you set above. RT has [https://docs.bestpractical.com/rt/latest/rt_perl.html additional documentation] on setting up your perl. Here’s what the different parts of the command are doing:

	* <code>make dirs</code> creates RT's directory structure, so we can install dependencies inside it.		* <code>make dirs</code> creates RT's directory structure, so we can install dependencies inside it.
Line 191:		Line 196:
	* <code>make install</code> installs all of RT’s files under <code>/opt/rt5</code> (or the prefix directory you set earlier). It will only run if <code>fixdeps</code> succeeded.		* <code>make install</code> installs all of RT’s files under <code>/opt/rt5</code> (or the prefix directory you set earlier). It will only run if <code>fixdeps</code> succeeded.

	Make sure you have <code>cd</code>ed into the RT source directory, ~~and~~ run:		Make sure you have <code>cd</code>ed into the RT source directory. To install the modules in the standard perl directories, run:

			<pre>sudo make dirs
			make fixdeps RT_FIX_DEPS_CMD="cpanm --sudo"
			sudo make install</pre>

			If you want to install the perl libraries in the RT directories, you could run:

	<pre>sudo make dirs		<pre>sudo make dirs
	make fixdeps RT_FIX_DEPS_CMD="cpanm --sudo --local-lib-contained=/opt/rt5/local"		make fixdeps RT_FIX_DEPS_CMD="cpanm --sudo --local-lib-contained=/opt/rt5/local"
	sudo make install</pre>		sudo make install</pre>

	If it works, the command will eventually output a message that says “Congratulations. RT is now installed.” followed by instructions about configuring and setting up the database. We’ll do that next.		If it works, the command will eventually output a message that says “Congratulations. RT is now installed.” followed by instructions about configuring and setting up the database. We’ll do that next.

Line 219:		Line 231:
	Set($WebPort, '443');		Set($WebPort, '443');
	# WebPath is the path where the RT web server runs on your WebDomain.		# WebPath is the path where the RT web server runs on your WebDomain.
	# Edit the path below if you're using a specific path.		# Edit the path below only if you're using a specific path like example.com/rt
	Set($WebPath, '/');		Set($WebPath, '/rt');

	# DatabaseUser is the name of the database account RT uses to read and store		# DatabaseUser is the name of the database account RT uses to read and store
Line 248:		Line 260:
	# You set all of RT's $LogTo* paramaters to a standard log level: 'debug',		# You set all of RT's $LogTo* paramaters to a standard log level: 'debug',
	# 'info', 'notice', 'warning', 'error', 'critical', 'alert', or 'emergency'.		# 'info', 'notice', 'warning', 'error', 'critical', 'alert', or 'emergency'.
	# For a modern install, ~~I recommend logging primarily~~ to syslog, so it goes		# For a modern install, if you log to syslog, it goes
	# to journald where it's easy to query and automatically gets rotated.		# to journald where it's easy to query and automatically gets rotated.
	Set($LogToSyslog, '~~info~~');		# Some syslogs log only warn and error, so lower levels like debug won't appear here.
			Set($LogToSyslog, 'warning');

	# When the RT server logs to stderr, that will go to the rt-server journal.		# When the RT server logs to stderr, that will go to the rt-server journal.
Line 256:		Line 269:
	# 'warning' or 'error' helps ensure you get notified if RT's cron jobs		# 'warning' or 'error' helps ensure you get notified if RT's cron jobs
	# encounter problems.		# encounter problems.
			# When running with Apache, these logs will go to the Apache error log,
			# which should be set up with logrotate automatically.
	Set($LogToSTDERR, 'warning');		Set($LogToSTDERR, 'warning');

Line 276:		Line 291:
	RT includes a tool to help you set up its database. By default, it connects to the database as an administrator to create the database and user that you configured in the previous step.		RT includes a tool to help you set up its database. By default, it connects to the database as an administrator to create the database and user that you configured in the previous step.

	(The instructions from <code>make install</code> and RT’s README file tell you to run <code>make initialize-database</code>. That ~~just~~ runs <code>rt-setup-database</code> for you. ~~Running the tool directly makes it easier to pass~~ the options ~~you need~~.)		The instructions from <code>make install</code> and RT’s README file tell you to run <code>make initialize-database</code>, so run:

			<pre>make initialize-database</pre>

			That runs the <code>rt-setup-database</code> command for you. If you're curious, you can see all of the options in [https://docs.bestpractical.com/rt/latest/rt-setup-database.html RT's documentation].

	* <code>--action=init</code> tells the tool to create the user, the database, the tables inside it, and insert core data RT needs to function.		* <code>--action=init</code> tells the tool to create the user, the database, the tables inside it, and insert core data RT needs to function.
	* '''If''' you are using an existing database server and the database ~~adminstrator~~ has already created the user account and database for RT, then you can add the <code>--skip-create</code> option.		* '''If''' you are using an existing database server and the database administrator has already created the user account and database for RT, then you can add the <code>--skip-create</code> option.
	* '''If''' you have a less common database setup, this tool has additional options to give you finer-grained control over what steps are run and how~~. Refer to [https://docs.bestpractical.com/rt/latest/rt-setup-database.html the full rt-setup-database documentation] to learn more about those~~.		* '''If''' you have a less common database setup, this tool has additional options to give you finer-grained control over what steps are run and how.
	* The command reads files from RT’s <code>etc/</code> directory by default, so the easiest way to run it is to <code>cd /opt/rt5</code> first, and then it will find the necessary files automatically.		* The command reads files from RT’s <code>etc/</code> directory by default, so the easiest way to run it is to <code>cd /opt/rt5</code> first, and then it will find the necessary files automatically.

	~~Run:~~

	~~<pre>cd /opt/rt5~~
	~~sudo sbin/rt-setup-database --action=init</pre>~~
	~~Enter the password for your database administrator account when prompted.~~

	=== Set up fulltext indexing ===		=== Set up fulltext indexing ===

Jbrandt at 14:30, 20 December 2022

2022-12-20T14:30:05Z

← Older revision		Revision as of 10:30, 20 December 2022
Line 3:		Line 3:
	This guide walks you through installing RT from source on a modern, popular Linux distro. Specifically, that means a distribution based on Debian or Red Hat that’s been released since around 2020.		This guide walks you through installing RT from source on a modern, popular Linux distro. Specifically, that means a distribution based on Debian or Red Hat that’s been released since around 2020.

	This guide is not meant to be followed step by step~~. It is meant as a resource to consult after choosing what~~ database and web server to use for RT.		RT's [https://docs.bestpractical.com/rt/latest/README.html README] for the version you are installing is the best starting resource. It provides the high-level steps to follow, but not details. This guide provides some of those details. It is not meant to be followed step by step, but it does provide guidance once you have picked the database and web server you want to use for RT.

	This guide assumes:		This guide assumes:
Line 45:		Line 45:
	== Install a database ==		== Install a database ==

	You need access to a database server. It can be remote, or you can install a database server alongside RT. RT supports ~~a few different databases~~, ~~but the best supported options~~ are ~~PostgreSQL~~ and ~~MariaDB~~.		You need access to a database server. It can be remote, or you can install a database server alongside RT. RT supports MySQL, MariaDB, Postgresql, and Oracle, and SQLite for development. Currently MariaDB and Postgreql are easiest to get and install via most Linux packaging systems.

	=== Installing and configuring the PostgreSQL server ===		=== Installing and configuring the PostgreSQL server ===

Bkembree at 21:48, 19 December 2022

2022-12-19T21:48:43Z

← Older revision		Revision as of 17:48, 19 December 2022
Line 346:		Line 346:
	\|}		\|}

	In the <code><VirtualHost></code> configuration blocks where you want to serve RT, add a configuration block like this, '''above''' any other <code>Alias</code>~~, <code>ProxyPass</code>,~~ or <code>ScriptAlias</code> lines:		In the <code><VirtualHost></code> configuration blocks where you want to serve RT, add a configuration block like this, '''above''' any other <code>Alias</code> or <code>ScriptAlias</code> lines:

	<pre>		<pre>
	# ~~SCRIPT_NAME~~ should match RT's WebPath~~, without~~ a ~~trailing~~ slash.		### Optional apache logs for RT
	# ~~This means when~~ WebPath is ~~/, it~~'s the ~~empty string ""~~.		# Ensure that your log rotation scripts know about these files
	~~ProxyFCGISetEnvIf true SCRIPT_NAME~~ ""		# ErrorLog /opt/rt5/var/log/apache2.error
	# ~~The location path in the first argument should match the~~ WebPath ~~in your~~		# TransferLog /opt/rt5/var/log/apache2.access
	# ~~RT site configuration. The network location~~ after ~~fcgi~~:~~// should match~~		# LogLevel debug
	# ~~the ListenStream in~~ rt-~~server.socket.~~
	~~ProxyPass / fcgi://localhost:5000~~/		AddDefaultCharset UTF-8

			# ScriptAlias and Location should match RT's WebPath

			# If WebPath is empty then use a single slash:
			ScriptAlias / /opt/rt5/sbin/rt-server.fcgi/
			# If WebPath is 'rt' then add that after the slash:
			# ScriptAlias /rt /opt/rt5/sbin/rt-server.fcgi/

			DocumentRoot "/opt/rt5/share/html"

			# If WebPath is empty then use a single slash:
			<Location />
			# If WebPath is 'rt' then add that after the slash:
			# <Location /rt>

			Require all granted
			Options +ExecCGI
			AddHandler fcgid-script fcgi
			</Location>
	</pre>		</pre>

Bkembree at 21:04, 18 December 2022

2022-12-18T21:04:01Z

Show changes

Brett: update LogToSTDERR explanation to match the rest of the deployment strategy

2022-10-21T19:48:36Z

update LogToSTDERR explanation to match the rest of the deployment strategy

← Older revision		Revision as of 15:48, 21 October 2022
Line 248:		Line 248:
	Set($LogToSyslog, 'info');		Set($LogToSyslog, 'info');

	# When the RT server logs to stderr, that ~~usually goes~~ to ~~your web~~ server's		# When the RT server logs to stderr, that will go to the rt-server journal.
	# ~~error log.~~ Command line tools log to their own stderr. Setting this to		# Command line tools log to their own stderr. Setting this to
	# 'warning' or 'error' helps ensure you get notified if RT's cron jobs		# 'warning' or 'error' helps ensure you get notified if RT's cron jobs
	# encounter problems.		# encounter problems.

Brett: small extra niceties in cron job scheduling

2022-10-12T17:45:55Z

small extra niceties in cron job scheduling

← Older revision		Revision as of 13:45, 12 October 2022
Line 541:		Line 541:
	/3 * * * rt /opt/rt5/sbin/rt-fulltext-indexer		/3 * * * rt /opt/rt5/sbin/rt-fulltext-indexer
	# Email out dashboards that users have subscribed to		# Email out dashboards that users have subscribed to
	0 * * * * rt /opt/rt5/sbin/rt-email-dashboards		1 * * * * rt /opt/rt5/sbin/rt-email-dashboards
	# Clean old sessions from the database		# Clean old sessions from the database
	10 3 * * * rt /opt/rt5/sbin/rt-clean-sessions --older 8d		50 3 * * * rt /opt/rt5/sbin/rt-clean-sessions --older 8d
	# Email out weekly digests for users who have requested it		# Email out weekly digests for users who have requested it
	50 4 * * Mon rt /opt/rt5/sbin/rt-email-digest -m weekly		50 4 * * Mon rt /opt/rt5/sbin/rt-email-digest -m weekly

Brett: update rt-mailgate install instructions for 5.0.3

2022-10-12T17:20:59Z

update rt-mailgate install instructions for 5.0.3

← Older revision		Revision as of 13:20, 12 October 2022
Line 529:		Line 529:
	Another common option is to periodically run a tool that fetches mail using a protocol like IMAP, like fetchmail or getmail, and passes it on to <code>rt-mailgate</code>. This is less common because it requires setting up another tool to run, and securely storing another set of mail server credentials. But it is useful when local policy prevents the RT server from receiving email directly.		Another common option is to periodically run a tool that fetches mail using a protocol like IMAP, like fetchmail or getmail, and passes it on to <code>rt-mailgate</code>. This is less common because it requires setting up another tool to run, and securely storing another set of mail server credentials. But it is useful when local policy prevents the RT server from receiving email directly.

	This is much less common, but it might help to know that <code>rt-mailgate</code> doesn’t have to run on the same system as RT itself. It just needs to be able to connect to RT’s web interface. If you don’t have any other options, you can install the RT software on a different system that receives email, and configure ''that'' system to run <code>rt-mailgate</code> and pass it on to the RT server. To do that, ~~just repeat~~ the ~~installation instructions above, skipping~~ the ~~steps about installing the database and web~~ server.		This is much less common, but it might help to know that <code>rt-mailgate</code> doesn’t have to run on the same system as RT itself. It just needs to be able to connect to RT’s web interface. If you don’t have any other options, you can install the RT software on a different system that receives email, and configure ''that'' system to run <code>rt-mailgate</code> and pass it on to the RT server. To do that, install the [https://metacpan.org/pod/RT::Client::CLI RT::Client::CLI] Perl package on the mail server. For example, you could install cpanminus, then run:

			<pre>cpanm --sudo RT::Client::CLI</pre>

	== Set up RT’s background jobs ==		== Set up RT’s background jobs ==

Brett: update for 5.0.3 release

2022-10-12T17:17:01Z

update for 5.0.3 release

← Older revision		Revision as of 13:17, 12 October 2022
Line 159:		Line 159:
	Download the latest source code using the link on the [https://bestpractical.com/download-page RT download page], extract it using <code>tar -xf</code>, and <code>cd</code> into the source code directory to run the rest of the commands in this section. For example:		Download the latest source code using the link on the [https://bestpractical.com/download-page RT download page], extract it using <code>tar -xf</code>, and <code>cd</code> into the source code directory to run the rest of the commands in this section. For example:

	<pre>curl -O https://download.bestpractical.com/pub/rt/release/rt-5.0.2.tar.gz		<pre>curl -O https://download.bestpractical.com/pub/rt/release/rt-5.0.3.tar.gz
	tar -xf rt-5.0.2.tar.gz		tar -xf rt-5.0.3.tar.gz
	cd rt-5.0.2</pre>		cd rt-5.0.3</pre>

	=== Pre-configure RT ===		=== Pre-configure RT ===
Line 309:		Line 309:
	All of RT’s configuration files should be readable by the user that runs the web server, and no other users, in order to protect sensitive information like the database password. RT provides a command to set permissions appropriately according to your distribution and configuration. <code>cd</code> to the directory where you extracted the RT source code, and run:		All of RT’s configuration files should be readable by the user that runs the web server, and no other users, in order to protect sensitive information like the database password. RT provides a command to set permissions appropriately according to your distribution and configuration. <code>cd</code> to the directory where you extracted the RT source code, and run:

	<pre>cd rt-5.0.2		<pre>cd rt-5.0.3
	sudo make fixperms</pre>		sudo make fixperms</pre>
	=== Verify the installation ===		=== Verify the installation ===

Brett: prefer a static User to avoid NoNewPrivileges and problems with sendmailpipe

2022-10-12T17:15:38Z

prefer a static User to avoid NoNewPrivileges and problems with sendmailpipe

← Older revision		Revision as of 13:15, 12 October 2022
Line 148:		Line 148:
	== Install RT ==		== Install RT ==

	=== Create an RT system ~~group~~ ===		=== Create RT system accounts ===

	This ~~group~~ will be used throughout the install process to control access to sensitive files. Run:		This account will be used throughout the install process to control access to sensitive files. Run:

	<pre>sudo groupadd --system rt</pre>		<pre>sudo groupadd --system rt
			sudo useradd --system --home-dir=/opt/rt5/var --gid=rt rt</pre>

	=== Get and unpack the RT source code ===		=== Get and unpack the RT source code ===
Line 161:		Line 162:
	tar -xf rt-5.0.2.tar.gz		tar -xf rt-5.0.2.tar.gz
	cd rt-5.0.2</pre>		cd rt-5.0.2</pre>

	=== Pre-configure RT ===		=== Pre-configure RT ===

Line 168:		Line 170:
	* <code>--prefix=/opt/rt5</code> sets the directory where RT will install all of its libraries, tools, and supporting files. You can choose another path if you like.		* <code>--prefix=/opt/rt5</code> sets the directory where RT will install all of its libraries, tools, and supporting files. You can choose another path if you like.
	* <code>--with-db-type=TYPE</code> - Replace <code>TYPE</code> with <code>Pg</code> for PostgreSQL, or <code>mysql</code> for MariaDB.		* <code>--with-db-type=TYPE</code> - Replace <code>TYPE</code> with <code>Pg</code> for PostgreSQL, or <code>mysql</code> for MariaDB.
	* <code>--with-web-group=rt</code> installs RT using the dedicated ~~group~~ we created earlier.		* <code>--with-web-user=rt --with-web-group=rt</code> installs RT using the dedicated accounts we created earlier.
	* The rest of the options tell RT to install additional dependencies for optional features.		* The rest of the options tell RT to install additional dependencies for optional features.

	Make sure you have <code>cd</code>ed into the RT source directory, and run:		Make sure you have <code>cd</code>ed into the RT source directory, and run:

	<pre>PERL="/usr/bin/env -S perl -I/opt/rt5/local/lib/perl5" ./configure --prefix=/opt/rt5 --with-db-type=TYPE --with-web-group=rt --with-attachment-store=disk --enable-externalauth --enable-gd --enable-graphviz --enable-gpg --enable-smime</pre>		<pre>PERL="/usr/bin/env -S perl -I/opt/rt5/local/lib/perl5" ./configure --prefix=/opt/rt5 --with-db-type=TYPE --with-web-user=rt --with-web-group=rt --with-attachment-store=disk --enable-externalauth --enable-gd --enable-graphviz --enable-gpg --enable-smime</pre>
	For more background, [https://docs.bestpractical.com/rt/latest/configure.html refer to the RT configure options documentation].		For more background, [https://docs.bestpractical.com/rt/latest/configure.html refer to the RT configure options documentation].

Line 261:		Line 263:
	1;		1;
	</pre>		</pre>

	<code>RT_SiteConfig.pm</code> is actually Perl code. RT runs the code directly to load the configuration. Any time you finish editing it, you can check that you didn’t make any syntax errors by running:		<code>RT_SiteConfig.pm</code> is actually Perl code. RT runs the code directly to load the configuration. Any time you finish editing it, you can check that you didn’t make any syntax errors by running:

Line 334:		Line 337:
	ExecStart=/usr/bin/multiwatch --forks=3 --signal=TERM -- /opt/rt5/sbin/rt-server.fcgi		ExecStart=/usr/bin/multiwatch --forks=3 --signal=TERM -- /opt/rt5/sbin/rt-server.fcgi
	StandardInput=socket		StandardInput=socket
	~~DynamicUser=true~~		User=rt
	~~SupplementaryGroups~~=rt
	UMask=027		UMask=027

Line 385:		Line 387:
	=== Enable the RT socket ===		=== Enable the RT socket ===

	~~Load the new services into RT, start~~ the server socket, and enable it on future boots:		Start the server socket and enable it on future boots:

	~~<pre>sudo systemctl daemon-reload~~
	~~sudo systemctl enable --now rt-server.socket</pre>~~

	~~== Alternative RT FastCGI service set up ==~~
	~~For me the guide don't work (Alma8.6). I had to add to rt-server.service~~
	~~<pre>SupplementaryGroups=rt postdrop~~
	~~ReadWritePaths=/opt/rt5/var /var/spool/postfix/maildrop~~
	~~</pre>~~
	~~but even then I couldn't use ''sendmailpipe'' . So I have implemented a simple solution~~

	~~Run:~~

	~~<pre>sudo systemctl edit --force --full rt-server.service</pre>~~

	~~This opens an editor to define the RT service to systemd. Use the editor to add this text to the file:~~

	~~<pre>[Unit]~~
	~~Description=RT FCGI server~~
	~~Before=nginx.service~~
	~~After=mariadb.service~~

	~~[Service]~~
	~~Type=simple~~
	~~ExecStart=/usr/bin/spawn-fcgi -n -u rt-server -g rt -a 127.0.0.1 -p 5000 -- /usr/bin/multiwatch -f 5 /opt/rt5/sbin/rt-server.fcgi~~

	~~[Install]~~
	~~WantedBy=multi-user.target~~
	~~</pre>~~

	~~For this you need to install ''spawn~~-~~fcgi'' and to add a dedicated user (for example~~ rt-server).		<pre>sudo systemctl enable --now rt-server.socket</pre>

	== Set up RT’s web server ==		== Set up RT’s web server ==
Line 564:		Line 537:
	<pre>		<pre>
	# Update the fulltext index with new ticket data		# Update the fulltext index with new ticket data
	/3 * * * ~~root~~ /opt/rt5/sbin/rt-fulltext-indexer		/3 * * * rt /opt/rt5/sbin/rt-fulltext-indexer
	# Email out dashboards that users have subscribed to		# Email out dashboards that users have subscribed to
	0 * * * * ~~root~~ /opt/rt5/sbin/rt-email-dashboards		0 * * * * rt /opt/rt5/sbin/rt-email-dashboards
	# Clean old sessions from the database		# Clean old sessions from the database
	10 3 * * * ~~root~~ /opt/rt5/sbin/rt-clean-sessions --older 8d		10 3 * * * rt /opt/rt5/sbin/rt-clean-sessions --older 8d
	# Email out weekly digests for users who have requested it		# Email out weekly digests for users who have requested it
	50 4 * * Mon ~~root~~ /opt/rt5/sbin/rt-email-digest -m weekly		50 4 * * Mon rt /opt/rt5/sbin/rt-email-digest -m weekly
	# Email out daily digests for users who have requested it		# Email out daily digests for users who have requested it
	50 5 * * * ~~root~~ /opt/rt5/sbin/rt-email-digest -m daily		50 5 * * * rt /opt/rt5/sbin/rt-email-digest -m daily
	</pre>		</pre>