$ sudo systemctl enable httpd mariadb postfix The second step is to start the web server and database server: $ sudo systemctl start httpd mariadb postfix The second line ensures that, after a restart, that port will remain open and available. The first line opens the port in the current configuration. $ sudo firewall-cmd -permanent -zone=public -add-service=http The first step is to open the standard port 80 in the firewall for the web server: $ sudo firewall-cmd -zone=public -add-service=http 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.

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. This can be disabled via the following command: # sudo setenforce 0 Some users have noted issues installing Redmine with SELinux active. $ sudo dnf install apr-devel apr-util-devel curl-devel gcc gcc-c++ git httpd httpd-devel ImageMagick-devel mariadb-devel mariadb-server nano postfix ruby-devel tar wget libxml2-devel libxslt-devel Disable SELinux apr-devel - For PassengerĪll of these can be installed prior to starting with a single command: Depending on your preferences, you may choose alternatives to some of these. If the kernel was updated as part of this command, you should perform a restart to begin using it: $ sudo shutdown -r nowīefore beginning the installation of Redmine, there are a number of dependencies which need to be installed.ĭepending on your needs, some of these may not be necessary. This can be done by issuing the following command: Updating the Systemīefore beginning, you should ensure all of your installed packages are up-to-date. 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. This guide can be used on top of an already existing system or, from scratch, downloading from the Fedora website.Īn ISO for installation can be downloaded from here. The hardware requirements are not significant, so a small VM with 10gb storage and 1GB ram and 1GB swap file should be sufficient. 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. No assumptions are made about the initial state of the system in this guide. Creating a Redmine Database and Account.How To Install Redmine-3.0.3 on Fedora 22.Exporting the data an databaseĪll the uploaded files are located in the “files” folder of Redmine, so we need to copy that over to the new server. (See how to install those plugins in the Redmine-Template Github repository). Ok so now is a good time to check if the plugins works well together, or if they require some changes The repository makes use of git sub-modules (.gitmodules) whenever possible so that code already publicly available is not pushed again in this repository. So it could easily be shared and updated when needed. This was a rather easy step, just listing the plugins that are still necessary, then finding their last stable version (if-any) that are compatible with Redmine 2.6.Īs this Redmine might not be the only one we have to deploy I decided to group the plugins we use in a Github repository Yay, a working Redmine stack! The plugins Sudo /opt/bitnami/ctlscript.sh restart apache Sudo /opt/bitnami/apps/redmine/bnconfig -disable_banner 1

Let’s do itĪll the following assume you are using a bitnami stack deployed under: So new OS, new Version, Update plugins, Missing plugins, new plugins… hopefully we did not change the Database too. Ubuntu 12.04 Running VirtualBox and DockerĪlso, quite a few plugins where added from the beginning, not all still in use so some plugins would have to be removed as well.

Our Redmine instance running quite a few plugins, upgrading to Redmine 3.0 wasn’t an option for compatibility issue, Now having a racked-server in our building data-center running VMs and docker apps, that was definitely our new host.

Redmine 2.5 (Stack was installed from the Bitnami native installer).

Windows Server 2008 R2 (The version does not actually matter).

Our Redmine server was firstly set-up on an available Windows Computer, and kept evolving from there. On this week nice adventure, I decided to have a clean, up-to-date instance of Redmine that would better fit in the current company infrastructure. Of the company that falls into my current responsibilities and to ensure the knowledge can be transferred properly. Some of the upcoming changes for me at work pushed to review all processes and infrastructure

Bitnami redmine restart apache