Redmine Version Compatibility
Redmineflux plugins support all Redmine versions. Always download Redmine from the official website to ensure you are running a stable, supported build.
Redmine 5.x Series
Redmine 6.x Series
Tip: Always use a release version from the official Redmine download page rather than a development build to ensure plugin compatibility and stability.
Official Redmine Installation Guide
The Ruby and Rails versions required for Redmineflux depend on the version of Redmine you have installed. Each Redmine release specifies the exact Ruby and Rails versions it supports.
Before installing any Redmineflux plugin, confirm that your Ruby and Rails versions match the requirements for your chosen Redmine version. Running incorrect versions is one of the most common causes of plugin loading failures and unexpected errors during installation.
Refer to the official Redmine installation documentation for the exact Ruby and Rails version matrix for your Redmine release. This ensures your environment is correctly configured before you add any plugins.
Test Your Environment with the Free Redmineflux Plugin
Before deploying paid Redmineflux plugins on a production environment, we strongly recommend installing one of the free Redmineflux plugins first. This approach allows you to validate three critical aspects of your setup without any risk:
Environment compatibility – Confirms that your Ruby, Rails, and Redmine versions are correctly configured and capable of loading Redmineflux plugins without errors.
Plugin folder structure – Verifies that the plugin is placed in the correct redmine/plugins directory and that the folder has not been renamed, which would prevent Redmine from recognising it.
Migration success – Validates that database migrations run to completion without errors and that all required plugin tables are created in the database before you proceed to paid plugins.
If the free plugin installs and operates correctly, your environment is ready for the full Redmineflux plugin suite.
Core Environment Requirements for Redmineflux
Before installing any Redmineflux plugin, ensure your environment meets all four of the following requirements:
A Fully Working Redmine Installation
Redmine must be installed and running without errors before any plugin is added. Attempting to install Redmineflux plugins on a broken or partially configured Redmine instance will result in errors that are difficult to diagnose. Complete the full Redmine setup and confirm the base application is stable before proceeding.
Correct Ruby & Rails Versions
Your Ruby and Rails versions must match the recommendations for your chosen Redmine version. Using incorrect versions is the most common cause of plugin loading failures. Refer to the official Redmine installation guide to confirm the exact versions required for your Redmine release before installing any plugins.
Supported Database Engine
Redmineflux plugins are compatible with the same database engines supported by Redmine itself. Ensure you are running one of the following:
Proper Plugin Folder Placement
All Redmineflux plugins must be placed in the redmine/plugins directory. Do not rename the plugin folder after downloading – Redmine uses the folder name to identify and load plugins, and renaming it will prevent the plugin from being recognised or loaded correctly.
Database Migration Requirement
Every Redmineflux plugin requires database migrations to be run during setup. These migrations create the necessary tables and fields in your database that the plugin depends on for all its functionality.
Important: A successful migration is mandatory. Missing or incomplete migrations will cause features to break or fail to appear within Redmine. Never skip this step during installation or after a plugin update.
To ensure a successful setup, follow these steps for every plugin installation:
Run all migration commands without errors. Execute the migration command for the plugin and monitor the output to confirm it completes without any failures or warnings.
Verify that all plugin tables are created in the database. After migrations complete, confirm the expected plugin tables exist in your database. Missing tables indicate a failed or incomplete migration.
Check logs to ensure no migration failures. Review your Redmine and database logs after running migrations to identify any errors that may not have been surfaced in the terminal output.
Re-run the migration if any table is missing. If plugin tables are absent after the initial migration, re-run the migration command. Address any errors before proceeding – do not start using the plugin until all tables are confirmed present.
Restart Redmine after installing or updating plugins. After installation and successful migration, restart the Redmine server to ensure all plugin components are loaded correctly into the running application.
Why These Requirements Matter
Redmineflux plugins are built to integrate deeply with Redmine’s core architecture – hooking into its routing, model layer, view system, and database schema. This deep integration is what enables the rich functionality that Redmineflux plugins provide, but it also means the environment must be precisely configured for everything to work correctly.
Running unsupported Ruby or Rails versions, skipping database migrations, or placing plugins in incorrect directories are the most common causes of installation issues. By ensuring your environment meets every requirement listed in this document before you begin, you avoid the vast majority of installation problems and ensure a smooth, reliable deployment of Redmineflux plugins in your Redmine instance.
Best practice: Validate your environment using a free Redmineflux plugin on a staging or test Redmine instance before installing paid plugins on production. This eliminates environment variables as a source of uncertainty and gives you confidence that the full plugin suite will install cleanly.
Conclusion
Meeting the system requirements for Redmineflux is straightforward when approached methodically. Ensure your Redmine installation is stable and running a supported version, confirm your Ruby and Rails versions match Redmine’s requirements, place plugins in the correct folder without renaming, and always run and verify database migrations before using any plugin.
If you have questions about compatibility or encounter issues during installation, our support team is available to help at support@redmineflux.com. You can also explore our documentation and free plugins to validate your environment before committing to a full deployment.