FedoraInstallation » History » Version 3
Jamie McPeek, 2014-08-16 22:06
1 | 1 | Jamie McPeek | h1. HowTo Install Redmine 2.5.x on Fedora 20 |
---|---|---|---|
2 | |||
3 | {{toc}} |
||
4 | |||
5 | h2. System Requirements |
||
6 | |||
7 | No assumptions are made about the initial state of the system in this guide. The guide can be followed for either 32-bit or 64-bit systems - though all testing and the original installation was performed on a 64-bit system. |
||
8 | |||
9 | The hardware requirements are not significant, so a small VM with 10gb storage and 1GB ram and 1GB swap file should be sufficient. |
||
10 | |||
11 | This guide can be used on top of an already existing system or, from scratch, downloading from the Fedora website. |
||
12 | |||
13 | An ISO for installation can be downloaded from "here":http://fedoraproject.org/en/get-fedora. |
||
14 | |||
15 | The rest of the guide assumes that you have created a user account with wheel/administrator access and are logged in to the terminal directly or through SSH. |
||
16 | 2 | Jamie McPeek | |
17 | h2. Updating the System |
||
18 | |||
19 | Before beginning, you should ensure all of your installed packages are up-to-date. This can be done by issuing the following command: |
||
20 | |||
21 | <pre> |
||
22 | $ sudo yum update |
||
23 | </pre> |
||
24 | |||
25 | If the kernel was updated as part of this command, you should perform a restart to begin using it: |
||
26 | |||
27 | <pre> |
||
28 | $ sudo shutdown -r now |
||
29 | </pre> |
||
30 | |||
31 | h2. Installing Dependencies |
||
32 | 3 | Jamie McPeek | |
33 | Before beginning the installation of Redmine, there are a number of dependencies which need to be installed. |
||
34 | |||
35 | Depending on your needs, some of these may not be necessary. |
||
36 | |||
37 | <pre> |
||
38 | apr-devel - For Passenger |
||
39 | apr-util-devel - For Passenger |
||
40 | curl-devel - For Passenger |
||
41 | gcc - For JSON |
||
42 | gcc-c++ - For Passenger |
||
43 | git - (Optional) For SCM Integration |
||
44 | httpd - Web Server |
||
45 | httpd-devel - For Passenger |
||
46 | ImageMagick-devel - For RMagick |
||
47 | mariadb-devel - For Redmine |
||
48 | mariadb-server - For Redmine |
||
49 | nano - Configuration Editor |
||
50 | ruby-devel - For Redmine |
||
51 | tar - For Decompression |
||
52 | wget - For Download |
||
53 | </pre> |
||
54 | |||
55 | All of these can be installed prior to starting with a single command: |
||
56 | |||
57 | <pre> |
||
58 | $ sudo yum install apr-devel apr-util-devel curl-devel gcc gcc-c++ git httpd httpd-devel ImageMagick-devel mariadb-devel mariadb-server nano ruby-devel tar wget |
||
59 | </pre> |
||
60 | |||
61 | h2. Disable SELinux |
||
62 | |||
63 | Some users have noted issues installing Redmine with SELinux active. This can be disabled via the following command: |
||
64 | |||
65 | <pre> |
||
66 | # sudo setenforce 0 |
||
67 | </pre> |
||
68 | |||
69 | Steps will be taken throughout the remainder of the guide to ensure that, if desired, SELinux can be re-enabled after and still maintain a fully functional Redmine installation. |
||
70 | |||
71 | h2. Enable Server Environment |
||
72 | |||
73 | With all of the dependencies installed, we need to ensure that the servers are setup, ready for use, and accessible external to the OS installation. |
||
74 | |||
75 | The first step is to open the standard port 80 in the firewall for the web server: |
||
76 | |||
77 | <pre> |
||
78 | $ sudo firewall-cmd --zone=public --add-service=http |
||
79 | $ sudo firewall-cmd --permanent --zone=public --add-service=http |
||
80 | </pre> |
||
81 | |||
82 | The first line opens the port in the current configuration. The second line ensures that, after a restart, that port will remain open and available. |
||
83 | |||
84 | The second step is to start the web server and database server: |
||
85 | |||
86 | <pre> |
||
87 | $ sudo systemctl start httpd mariadb |
||
88 | $ sudo systemctl enable httpd mariadb |
||
89 | </pre> |
||
90 | |||
91 | Similar to the firewall commands, the first line starts the servers in the current configuration. The second line ensures that, after a restart, both servers come back online. |