Request Tracker - Revision history

Zcrayfish: nowiki'd hypothetical URLs.

2023-08-25T03:34:04Z

nowiki'd hypothetical URLs.

← Older revision		Revision as of 03:34, 25 August 2023
Line 29:		Line 29:
	Set($WebDomain, 'fqdn.in.example.com');		Set($WebDomain, 'fqdn.in.example.com');
	Set($OwnerEmail, 'RTAdmin@example.com');		Set($OwnerEmail, 'RTAdmin@example.com');
	Set($LogoLinkURL, 'https://www.example.com/');		Set($LogoLinkURL, '<nowiki>https://www.example.com/</nowiki>');
	Set($LogoAltText, 'Example.com Support');		Set($LogoAltText, 'Example.com Support');
	# Set($LogoURL, '');		# Set($LogoURL, '');
Line 69:		Line 69:
	** mlmmj-sub -L /var/spool/mlmmj/support-list -a support@example.com -n		** mlmmj-sub -L /var/spool/mlmmj/support-list -a support@example.com -n
	* Add to ''/etc/postfix/master.cf'':		* Add to ''/etc/postfix/master.cf'':
	rt4 unix - n n - - pipe flags=DORhu user=lighttpd argv=/usr/bin/rt-mailgate --queue $nexthop --action correspond --url http://fqdn.in.example.com/		rt4 unix - n n - - pipe flags=DORhu user=lighttpd argv=/usr/bin/rt-mailgate --queue $nexthop --action correspond --url <nowiki>http://fqdn.in.example.com/</nowiki>
	mlmmj unix - n n - - pipe flags=DORhu user=mlmmj argv=/usr/bin/mlmmj-recieve -F -L /var/spool/mlmmj/$nexthop		mlmmj unix - n n - - pipe flags=DORhu user=mlmmj argv=/usr/bin/mlmmj-recieve -F -L /var/spool/mlmmj/$nexthop
	* Add to ''/etc/postfix/main.cf'':		* Add to ''/etc/postfix/main.cf'':
Line 110:		Line 110:
	== Final RT4 configuration ==		== Final RT4 configuration ==

	* Login to http://fqdn.in.example.com (your RT server)		* Login to <nowiki>http://fqdn.in.example.com</nowiki> (your RT server)
	** Add AdminCC for Support Users to support queue		** Add AdminCC for Support Users to support queue
	** New template called 'Support Users Correspondence' (anyone you add to Support Users group will have their outbound email rewritten to 'Support Team' instead of their realname		** New template called 'Support Users Correspondence' (anyone you add to Support Users group will have their outbound email rewritten to 'Support Team' instead of their realname
Line 160:		Line 160:
	** Those emails are either created as a new ticket in RT, or if the subject line contains a ticket ID, then it's inserted into the appropriate ticket		** Those emails are either created as a new ticket in RT, or if the subject line contains a ticket ID, then it's inserted into the appropriate ticket
	** Ticket comments and correspondence will be sent on to support-list@example.com, which is an mlmmj list, which can be subscribed to using support-list+subscribe@example.com		** Ticket comments and correspondence will be sent on to support-list@example.com, which is an mlmmj list, which can be subscribed to using support-list+subscribe@example.com
	** The RT4 web interface is available at http://fqdn.in.example.com		** The RT4 web interface is available at <nowiki>http://fqdn.in.example.com</nowiki>

	[[Category:Mail]]		[[Category:Mail]]

Zcrayfish: Used canonical URL.

2023-08-07T19:29:55Z

Used canonical URL.

← Older revision		Revision as of 19:29, 7 August 2023
Line 1:		Line 1:
	This guide will get [https://bestpractical.com/~~rt/~~ Request Tracker] 4 setup working, with support for emails sent to an mlmmj mailing list to be inserted first into the ticket system, then sent on to mlmmj. It is intended for a HelpDesk-type deployment. This howto assumes that you have a working postfix setup already. <br />		This guide will get [https://bestpractical.com/request-tracker Request Tracker] 4 setup working, with support for emails sent to an mlmmj mailing list to be inserted first into the ticket system, then sent on to mlmmj. It is intended for a HelpDesk-type deployment. This howto assumes that you have a working postfix setup already. <br />

	Note: This document has been tested on Alpine Linux 2.2.2, but contains some packages which are currently in the [[Repositories#Edge\|edge]] repository.<br />		Note: This document has been tested on Alpine Linux 2.2.2, but contains some packages which are currently in the [[Repositories#Edge\|edge]] repository.<br />

Sertonix: use https links

2023-08-07T11:37:15Z

use https links

← Older revision		Revision as of 11:37, 7 August 2023
Line 1:		Line 1:
	This guide will get [~~http~~://bestpractical.com/rt/ Request Tracker] 4 setup working, with support for emails sent to an mlmmj mailing list to be inserted first into the ticket system, then sent on to mlmmj. It is intended for a HelpDesk-type deployment. This howto assumes that you have a working postfix setup already. <br />		This guide will get [https://bestpractical.com/rt/ Request Tracker] 4 setup working, with support for emails sent to an mlmmj mailing list to be inserted first into the ticket system, then sent on to mlmmj. It is intended for a HelpDesk-type deployment. This howto assumes that you have a working postfix setup already. <br />

	Note: This document has been tested on Alpine Linux 2.2.2, but contains some packages which are currently in the [[Repositories#Edge\|edge]] repository.<br />		Note: This document has been tested on Alpine Linux 2.2.2, but contains some packages which are currently in the [[Repositories#Edge\|edge]] repository.<br />
Line 7:		Line 7:

	* add edge/main repository to /etc/apk/repositories		* add edge/main repository to /etc/apk/repositories
	{{Cmd\|printf "~~http~~://nl.alpinelinux.org/alpine/edge/main" >> /etc/apk/repositories		{{Cmd\|printf "https://nl.alpinelinux.org/alpine/edge/main" >> /etc/apk/repositories
	apk update}}		apk update}}
	* {{Cmd\|apk add lighttpd fcgi postgresql rt4 postfix postfix-pcre mlmmj}}		* {{Cmd\|apk add lighttpd fcgi postgresql rt4 postfix postfix-pcre mlmmj}}
Line 29:		Line 29:
	Set($WebDomain, 'fqdn.in.example.com');		Set($WebDomain, 'fqdn.in.example.com');
	Set($OwnerEmail, 'RTAdmin@example.com');		Set($OwnerEmail, 'RTAdmin@example.com');
	Set($LogoLinkURL, '~~http~~://www.example.com/');		Set($LogoLinkURL, 'https://www.example.com/');
	Set($LogoAltText, 'Example.com Support');		Set($LogoAltText, 'Example.com Support');
	# Set($LogoURL, '');		# Set($LogoURL, '');

Encode: Change link to Repositories page

2022-06-27T02:02:35Z

Change link to Repositories page

← Older revision		Revision as of 02:02, 27 June 2022
Line 1:		Line 1:
	This guide will get [http://bestpractical.com/rt/ Request Tracker] 4 setup working, with support for emails sent to an mlmmj mailing list to be inserted first into the ticket system, then sent on to mlmmj. It is intended for a HelpDesk-type deployment. This howto assumes that you have a working postfix setup already. <br />		This guide will get [http://bestpractical.com/rt/ Request Tracker] 4 setup working, with support for emails sent to an mlmmj mailing list to be inserted first into the ticket system, then sent on to mlmmj. It is intended for a HelpDesk-type deployment. This howto assumes that you have a working postfix setup already. <br />

	Note: This document has been tested on Alpine Linux 2.2.2, but contains some packages which are currently in the [[Edge\|edge~~/testing~~]] repository.<br />		Note: This document has been tested on Alpine Linux 2.2.2, but contains some packages which are currently in the [[Repositories#Edge\|edge]] repository.<br />
	Note: Use a computer with at least 512MB of RAM.<br />		Note: Use a computer with at least 512MB of RAM.<br />

Larena: Fix syntax of latest versions of postgresql-client utilities

2015-05-29T11:25:52Z

Fix syntax of latest versions of postgresql-client utilities

← Older revision		Revision as of 11:25, 29 May 2015
Line 13:		Line 13:
	* {{Cmd\|/etc/init.d/postgresql setup}}		* {{Cmd\|/etc/init.d/postgresql setup}}
	* {{Cmd\|/etc/init.d/postgresql start}}		* {{Cmd\|/etc/init.d/postgresql start}}
	* {{Cmd\|su - postgres -c "createuser -P"}}		* {{Cmd\|su - postgres -c "createuser -P rt_user"}}
	~~Enter name of role to add: '''rt_user'''~~
	Enter password for new role: '''''rtpass'''''		Enter password for new role: '''''rtpass'''''
	Enter it again: '''''rtpass'''''		Enter it again: '''''rtpass'''''
Line 51:		Line 50:
	Set($SetOutgoingMailFrom, 1);		Set($SetOutgoingMailFrom, 1);
	Set($FriendlyFromLineFormat, '"%s" <%s>');		Set($FriendlyFromLineFormat, '"%s" <%s>');
	* {{Cmd\|/usr/sbin/rt-setup-database --action init}}		* {{Cmd\|/usr/sbin/rt-setup-database --action init --dba postgres}}
	* {{Cmd\|rt-server}}		* {{Cmd\|rt-server}}
	* Test and make sure that you can access rt using the built-in webserver first.		* Test and make sure that you can access rt using the built-in webserver first.

Larena: supply datadir for RT db upgrade

2014-02-14T09:28:13Z

supply datadir for RT db upgrade

← Older revision		Revision as of 09:28, 14 February 2014
Line 170:		Line 170:
	Upgrading the web interfaces should be easy as upgrading any Alpine package		Upgrading the web interfaces should be easy as upgrading any Alpine package
	{{Cmd\|apk add -u rt4}}		{{Cmd\|apk add -u rt4}}
	~~"rt-setup-database" expects to find the upgrade data in "./etc/upgrade" as in source tarball. Hence before launching the actual DB upgrade do:~~
	~~{{Cmd\|cd /root && mkdir etc}}~~
	~~{{Cmd\|cp -R /etc/rt4/upgrade etc}}~~
	Now upgrade the database:		Now upgrade the database:
	{{Cmd\|rt-setup-database --dba postgres --action upgrade}}		{{Cmd\|rt-setup-database --dba postgres --datadir /etc/rt4/upgrade --action upgrade}}
	Answers to the questions asked.		Answers to the questions asked.

Larena: upgrade RT section added

2014-02-12T14:09:38Z

upgrade RT section added

← Older revision		Revision as of 14:09, 12 February 2014
Line 166:		Line 166:
	[[Category:Server]]		[[Category:Server]]
	[[Category:Programming]]		[[Category:Programming]]

			== Upgrading RT ==
			Upgrading the web interfaces should be easy as upgrading any Alpine package
			{{Cmd\|apk add -u rt4}}
			"rt-setup-database" expects to find the upgrade data in "./etc/upgrade" as in source tarball. Hence before launching the actual DB upgrade do:
			{{Cmd\|cd /root && mkdir etc}}
			{{Cmd\|cp -R /etc/rt4/upgrade etc}}
			Now upgrade the database:
			{{Cmd\|rt-setup-database --dba postgres --action upgrade}}
			Answers to the questions asked.

Fab: Request-Tracker moved to Request Tracker

2012-05-23T12:25:14Z

Request-Tracker moved to Request Tracker

← Older revision	Revision as of 12:25, 23 May 2012
(No difference)

Fab at 12:24, 23 May 2012

2012-05-23T12:24:55Z

← Older revision		Revision as of 12:24, 23 May 2012
Line 1:		Line 1:
	This guide will get Request Tracker 4 setup working, with support for emails sent to an mlmmj mailing list to be inserted first into the ticket system, then sent on to mlmmj. It is intended for a HelpDesk-type deployment. This howto assumes that you have a working postfix setup already. <br />		This guide will get [http://bestpractical.com/rt/ Request Tracker] 4 setup working, with support for emails sent to an mlmmj mailing list to be inserted first into the ticket system, then sent on to mlmmj. It is intended for a HelpDesk-type deployment. This howto assumes that you have a working postfix setup already. <br />

	Note: This document has been tested on Alpine Linux 2.2.2, but contains some packages which are currently in the [[~~http://wiki.alpinelinux.org/wiki/Upgrading_to_Edge~~ edge/testing ~~repository~~]].<br />		Note: This document has been tested on Alpine Linux 2.2.2, but contains some packages which are currently in the [[Edge\|edge/testing]] repository.<br />
	Note: Use a computer with at least 512MB of RAM.<br />		Note: Use a computer with at least 512MB of RAM.<br />

Dubiousjim: Category:Programming

2012-03-26T11:28:41Z

Category:Programming

← Older revision		Revision as of 11:28, 26 March 2012
Line 165:		Line 165:
	[[Category:Mail]]		[[Category:Mail]]
	[[Category:Server]]		[[Category:Server]]
			[[Category:Programming]]