UbuntuにRedmine 5.1/Ruby 2.7をインストールする

sudo adduser redmine

sudo gpasswd -a redmine sudo

sudo apt update

sudo apt upgrade -y

sudo apt install -y build-essential git vim

cd ~
wget https://dev.mysql.com/get/mysql-apt-config_0.8.29-1_all.deb
sudo dpkg -i mysql-apt-config_0.8.29-1_all.deb

sudo apt update

sudo apt install -y mysql-server libmysqlclient-dev

systemctl status mysql

● mysql.service - MySQL Community Server
     Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2022-06-17 06:53:26 UTC; 16s ago
       Docs: man:mysqld(8)
             http://dev.mysql.com/doc/refman/en/using-systemd.html
   Main PID: 26378 (mysqld)
     Status: "Server is operational"
      Tasks: 38 (limit: 4575)
     Memory: 359.0M
     CGroup: /system.slice/mysql.service
             └─26378 /usr/sbin/mysqld

sudo mysql_secure_installation

redmine@redmine-test:~$ sudo mysql_secure_installation

Securing the MySQL server deployment.

Enter password for user root:

VALIDATE PASSWORD COMPONENT can be used to test passwords
and improve security. It checks the strength of password
and allows the users to set only those passwords which are
secure enough. Would you like to setup VALIDATE PASSWORD component?

Press y|Y for Yes, any other key for No: N
Using existing password for root.
Change the password for root ? ((Press y|Y for Yes, any other key for No) : N

 ... skipping.
By default, a MySQL installation has an anonymous user,
allowing anyone to log into MySQL without having to have
a user account created for them. This is intended only for
testing, and to make the installation go a bit smoother.
You should remove them before moving into a production
environment.

Remove anonymous users? (Press y|Y for Yes, any other key for No) : Y
Success.


Normally, root should only be allowed to connect from
'localhost'. This ensures that someone cannot guess at
the root password from the network.

Disallow root login remotely? (Press y|Y for Yes, any other key for No) : Y
Success.

By default, MySQL comes with a database named 'test' that
anyone can access. This is also intended only for testing,
and should be removed before moving into a production
environment.


Remove test database and access to it? (Press y|Y for Yes, any other key for No) : Y
 - Dropping test database...
Success.

 - Removing privileges on test database...
Success.

Reloading the privilege tables will ensure that all changes
made so far will take effect immediately.

Reload privilege tables now? (Press y|Y for Yes, any other key for No) : Y
Success.

mysql -u root -p

CREATE DATABASE redmine CHARACTER SET utf8mb4;
CREATE USER 'redmine'@'localhost' IDENTIFIED BY 'my_password';

GRANT ALL PRIVILEGES ON redmine.* TO 'redmine'@'localhost';
FLUSH PRIVILEGES;
EXIT;

sudo apt install -y rbenv

rbenv init

# Load rbenv automatically by appending
# the following to ~/.bashrc:
eval "$(rbenv init -)"

cd ~
vim .bashrc

source .bashrc

cd ~
mkdir -p "$(rbenv root)"/plugins
git clone https://github.com/rbenv/ruby-build.git "$(rbenv root)"/plugins/ruby-build
curl -fsSL https://github.com/rbenv/rbenv-installer/raw/main/bin/rbenv-doctor | bash

Checking for `rbenv' in PATH: /usr/bin/rbenv
Checking for rbenv shims in PATH: OK
Checking `rbenv install' support: /home/redmine/.rbenv/plugins/ruby-build/bin/rbenv-install (ruby-build 20211203)
Counting installed Ruby versions: none
  ...
Auditing installed plugins: OK

rbenv install --list

rbenv install 2.7.8
rbenv global 2.7.8

ruby -v

cd ~
wget https://www.redmine.org/releases/redmine-5.1.2.tar.gz

cd /opt
sudo tar xvf ~/redmine-5.1.2.tar.gz

sudo ln -s redmine-5.1.2 redmine

sudo chown -R redmine:redmine redmine/

cd /opt
sudo cp redmine/config/database.yml.example redmine/config/database.yml

sudo vim redmine/config/database.yml

production:
  adapter: mysql2
  database: redmine
  host: localhost
  username: redmine
  password: "<password>"
  encoding: utf8mb4

cd /opt/redmine
bundle config set --local without 'development test'
bundle install

RAILS_ENV=production bundle exec rake generate_secret_token

RAILS_ENV=production bundle exec rake db:migrate
RAILS_ENV=production bundle exec rake redmine:load_default_data

Select language: ar, az, bg, bs, ca, cs, da, de, el, en, en-GB, es, es-PA, et, eu, fa, fi, fr, gl, he, hr, hu, id, it, ja, ko, lt, lv, mk, mn, nl, no, pl, pt, pt-BR, ro, ru, sk, sl, sq, sr, sr-YU, sv, th, tr, uk, vi, zh, zh-TW [en] en

cd /opt/redmine
bundle exec rails server -u webrick -e production

http://<サーバーアドレス>:3000

cd /opt/redmine
sudo vim Gemfile.local

gem 'puma'

bundle install

Your Gemfile lists the gem puma (>= 0) more than once.
You should probably keep only one of them.
Remove any duplicate entries and specify the gem only once.
While it's not a problem now, it could cause errors if you change the version of one of them later.

bundle exec puma -e production

http://<サーバーアドレス>:9292

cd /opt/redmine
sudo vim Gemfile.local

gem 'rack-cors'

bundle install

sudo vim config/initializers/cors.rb

Rails.application.config.middleware.insert_before 0, Rack::Cors do
  allow do
    origins '*'
    resource '*', headers: :any, methods: [:get, :post, :patch, :put, :delete, :options]
  end
end

cd ~
openssl genrsa -out private.key 2048
openssl req -new -key private.key -out request.csr

openssl x509 -in request.csr -out certificate.crt -req -signkey private.key -days 365

cd /opt/redmine
bundle exec puma -b 'ssl://0.0.0.0:9393?key=/home/redmine/private.key&cert=/home/redmine/certificate.crt' -e production

https://<サーバーアドレス>:9393

cd ~
vim start_redmine.sh

#!/bin/sh

cd /opt/redmine
/home/redmine/.rbenv/shims/bundle exec rails server -u webrick -e production

chmod +x start_redmine.sh

sudo vim /lib/systemd/system/redmine.service

[Unit]
Description=Start Redmine Server
After=network.target

[Service]
Type=simple
ExecStart=/home/redmine/start_redmine.sh
Restart=always

[Install]
WantedBy=multi-user.target

sudo systemctl enable redmine

sudo systemctl start redmine