googleredmine

Install plugins

Before installing a plugin, make sure that the plugin is compatible with your Redmine version. For plugins from the Redmine Plugin Directory. Select your Redmine version and check if the plugin is compatible or not with your version using the drop down menu located in the top right margin: “Show only plugins compatible with Redmine: version”.

NOTE: If you connected to the instance via the Google Cloud Console, you will need to change your user to the bitnami user. Insert the following command before executing the steps below: sudo su bitnami

  • Navigate to the Redmine installation directory:

      $ cd /opt/bitnami/redmine
    
  • Navigate to the plugins directory and get the .zip file or clone the plugin’s Git repository:

      $ cd plugins
    
  • If you have obtained a .zip file, uncompress it and then delete the original file. Remember to replace PLUGIN_NAME-x-y-z with the correct name and version of the plugin:

      $ unzip PLUGIN_NAME-x-y-z.zip
      $ rm PLUGIN_NAME-x-y-z.zip
    

    IMPORTANT: Before installing the plugin, check the installation notes in the plugin description or README. Some plugins need special installation requirements.

  • Navigate to the Redmine installation directory and install the plugin:

      $ cd -
      $ bundle install
      $ bundle exec rake redmine:plugins NAME=PLUGIN_NAME RAILS_ENV=production
    

    NOTE: It could display a warning message about the log production file. In that case, run the following commands:

    $ sudo chown :bitnami log/production.log
    $ sudo chmod g+w log/production.log
    
  • Restart Apache services:

      $ sudo /opt/bitnami/ctlscript.sh restart
    

Troubleshooting plugin installation

  • If you receive an error like this in Redmine 2.4.0-0 and newer:

    You are trying to install in deployment mode after changing your Gemfile. Run ‘bundle install’ elsewhere and add the updated Gemfile.lock to version control.

    Try adding the --no-deployment argument to the bundle install command as suggested in the error message.

Last modification February 9, 2023