Redmine installation process detailed problem management system


Detailed explanation of installation process of redmine problem management system

In the process of program development, we often need a perfect bug management system to improve the efficiency of development and bug tracking. Here, we suggest to use redmine (I think the function is more comprehensive). The construction process is a little more complicated, and the online search is not comprehensive enough. Here we will describe the build process in detail.

The first step is to install ruby

  • Apt (Debian or Ubuntu)
sudo apt-get install ruby-full
  • Yum (CentOS, Fedora, or RHEL)
sudo yum install ruby
The version installed here is 2.0.0, which is too low. An error may be reported in the later installation process. It is recommended to use compile installation in centeros

Manual compilation and installation 2.3.6
tar zxvf ruby-2.3.6.tar.gz
cd ruby-2.3.6
./confgiue -pirfix=/usr/local/
make && make install

Step 2 rubygems installation

cd rubygems-2.7.4
ruby setup.rb

Step 3 rake installation

gem install rake

Step 4 rails installation

gem install rails

Step 5 redmine installation

We need to pay attention here, because there will be many errors in the installation process, which are described in detail below.

cd redmine-3.4.4/conf
Will * * yml.example  Make a copy of the file, and it becomes * *. YML
  • Change database configuration file database.yml
  • Execute bundle install
Error "make sure that ` gem install rmagick - V '2.16.0' ` successes before bundling."
  • Solve the above error problems
Unbun system apt get install imagemagic libmagickwand dev  
Centeros system 
    yum install ImageMagick 
    yum install ImageMagick-devel

gem install rmagick -v '2.16.0'

bundle install

Note: steps 6, 7 and 8 need to be executed in the redmine / conf directory

Step 6 create the database redmine_ development

create database redmine_development;

Step 7 create the table

It is created to redmine by default_ Development this library
rake db:migrate
  • Note: at this time, the database code is not utf8 and cannot be entered in Chinese. All tables need to be changed to utf8 code.

Step 8 create in the conf directory secrets.yml file

The format is as follows
  secret_key_base: 'XXXXXXX'

  secret_key_base: 'XXXXXXX'

# Do not keep production secrets in the repository,
# instead read values from the environment.
    secret_key_base: 'XXXXXXX'
  • Execute the command of rails to generate secret key in conf Directory: rake secret rails_ Env = production, a secret key will be generated. Fill in the XXX above

Installation complete start service

rails s -b -p 82 -d the local boot IP can be changed to the corresponding IP

82 is the boot port of the specified service, which can be changed by yourself
  • If the external network cannot be accessed, please check the firewall configuration or the security group configuration of the cloud server.

The above is my own practice. Both Ubuntu and centeros are successfully deployed.