forked from jfcanaveral/docker-rt
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathREADME
70 lines (53 loc) · 1.52 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
docker-rt
=========
This is a docker image for running Best Practical's RT (Request Tracker), a
ticket tracking system.
It's currently a work in progress, but it includes
RT
nginx
postfix + spamassassin
And exposes the RT web interface on container port 80 and an RT-connected MTA on
container port 25.
from scratch
------------
Start a postgres container:
docker run \
--name rtdb \
-e POSTGRES_USER=rt_user \
-e POSTGRES_PASSWORD=rt_pass \
-e POSTGRES_DB=rt4 \
-d postgres
Run a one-off container to configure the database:
docker run \
--link rtdb:db \
-e DATABASE_USER=rt_user \
-e DATABASE_PASSWORD=rt_pass \
-e DATABASE_NAME=rt4 \
tutems/request-tracker \
/usr/bin/rtinit
Now the database is initialised and you can run RT proper:
docker run -d \
--link rtdb:db \
--name rt \
-p 25 \
-p 80 \
-e DATABASE_USER=rt_user \
-e DATABASE_PASS=rt_pass \
-e DATABASE_NAME=rt4 \
tutems/request-tracker
To see the ports on which the web and mail interfaces are exposed, run `docker ps`.
run against a pre-existing database
-----------------------------------
You can provide the DATABASE_HOST directly:
docker run -d \
-p 25 \
-p 80 \
-e DATABASE_HOST=dbserver \
-e DATABASE_USER=rt_user \
-e DATABASE_PASSWORD=rt_pass \
-e DATABASE_NAME=rt4 \
tutems/request-tracker
configuration
-------------
This image provides some limited support for customising the deployment using
environment variables. See RT_SiteConfig.pm for details.