Redmine

Redmine is a flexible project management web application. Written using the Ruby on Rails framework, it is cross-platform and cross-database.

Redmine is open source and released under the terms of the GNU General Public License v2 (GPL).

• Redmine package information

Requirements

Check the Redmine requirements carefully, specially if you won't use PostgreSQL. A few MariaDB and MySQL issues remain open.

Installation

Redmine database and application

This was tested in Debian Stretch (9) / Buster (10).

1. Install your database:

apt install postgresql # or default-mysql-server

2. Install Redmine with support for your database of choice:

apt install redmine-pgsql # or redmine-mysql, or redmine-sqlite

apt install redmine-pgsql -t buster-backports # or redmine-mysql, or redmine-sqlite

This will also install all required dependencies including Ruby libraries, etc.

There will be one or more prompts asking to confirm database configuration via dbconfig-common. The default Yes should be OK unless you are using an external database or want to otherwise manually configure this.

3. Configure the web server

apt install apache2 libapache2-mod-passenger

To use your domain for Redmine only (ie. http://domain.com/):

cp /usr/share/doc/redmine/examples/apache2-passenger-host.conf /etc/apache2/sites-available/redmine.conf

To use the same domain shared with other applications (ie. http://domain.com/redmine):

cp /usr/share/doc/redmine/examples/apache2-passenger-alias.conf /etc/apache2/sites-available/redmine.conf

Edit your configuration file to add your domain name and sysadmin contact information:

edit /etc/apache2/sites-available/redmine.conf

For example:

    ServerName exampledomain.com
    ServerAdmin admin@exampledomain.com

Next:

a2enmod passenger
a2ensite redmine.conf
a2dissite 000-default
service apache2 reload

Alternatively, to use the same domain but a different port, base your config on apache2-passenger-host.conf, then edit apache2.conf to also Listen to <port> and redmine.conf accordingly. In this case disabling 000-default is not required.

4. Log into Redmine at http://<ip>/ with the following default admin account:

username: admin
password: admin

TLS certificate

1. Add the Debian Backports repository

2. Follow instructions at the Certbot documentation

Differences from upstream Redmine

The Debian redmine package contains a few patches to support running multiple Redmine instances using a single codebase. You manage your instances by using dpkg-reconfigure redmine. This multi-instance support makes some things appear in places that are different from when you are using the upstream Redmine:

• The application logs are located under /var/log/redmine/${instance}/ (instead of /path/to/redmine/log)

• The database configuration is located at /etc/redmine/${instance}/database.yml (instead of /path/to/redmine/config/database.yml)

• File attachments are located under /var/lib/redmine/${instance}/files

• Plugins should be placed under /usr/share/redmine/plugins. The folder doesn't exist by default and must be created. Don't use /usr/share/redmine/lib/plugins as this result to routing error in the application.

Buster (Debian 10)

Apache 2.4.29

Create /etc/apache2/conf-available/redmine.conf

Example configuration:

Alias /redmine /your_redmine/public
<Location /redmine>
     PassengerBaseURI /redmine
     PassengerAppRoot /your_redmine/
</Location>
<Directory /your_redmine/public>
    Require all granted
    Allow from all
    AllowOverride all
    RailsBaseURI /redmine
    RailsEnv production
    Options -MultiViews
</Directory>

sudo a2enconf redmine
sudo service apache2 reload

RVM

RVM should make it easier to manage Ruby versions. So, when the Debian gems were down, it already happened to me with Debian, it was with RVM on Debian that I was able to install Redmine to continue using the program and the data.

The Debian documentation is far too rudimentary. Call to contributors. How to back up, update the database for the new version of Redmine. We do not know where we are going, as a new user. How to position yourself to follow the evolution of Redmine and stick to the official versions?

The following tutorial, in French, has been rewritten and completed on the basis of an English tutorial. It includes the installation as well as the updating of the database. Use at your own risk in production, but, no less dangerous than to pass a Debian package in production, if there is no documentation that goes with it and should be kept up to date, to stick to the problems that may be encountered ( Problems of gems and output of packages that are not available, user running the service, rights on files, installation of plugins ...).

The RVM deployment is an alternative that will allow you to install Redmine on Debian, and always be able to update the database for the latest version of Redmine.

If another place on the wiki is more suitable to present this installation with RVM, please move this part, but do not delete. This tutorial allows many ways to run Redmine in a simple, and fast way: installation, update of the database, add a template, add plugins.

If information is missing, or if there are security risks to using RVM, you can test and contribute to clearly indicate the benefits and shortcomings of this solution.

For the moment, the information about Redmine, are too rudimentary to allow me to get to install Redmine, then, a plugin, with a system user. It may seem simple, but, all the tutorials I've seen present the thing differently, and, few are functional, unlike this tutorial that puts forward the RVM solution. Thank you for considering the lack of information on this page, and for inspiring you with information on the RVM tutorial, to complete the Debian Redmine page.

[[https://wiki.visionduweb.fr/index.php?title=Installer_Redmine_sur_Debian_avec_RVM |RVM with Debian, in French]]

CategorySystemAdministration CategorySystemAdministration