Support option -d to set xapian index database via CLI #1520
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For running xapian indexer it is necessary to configure it to use the same database for indexing as defined in the user interface on plugin settings.
In order to make the configuration of xapian indexer some kind of persistence the command line options in
redmine_dmsf/extra/xapian_indexer.rb
could be extended by providing a further option for the index database path:With this additional option it is possible to move the index database outside of redmine root to keep it even after running updates. Furthermore, custom configuration in
redmine_dmsf/extra/xapian_indexer.rb
won't be overridden when updating this plugin.