Allow repository-specific / client-side ignore specifiers (kinda like .gitignore)

[sagarkhushalani]

Is your feature request related to a problem? Please describe.
We have multiple large projects that get grok'd. Different teams have different requirements for what they would like excluded from the grok index. It would be easier if we could just have the team add a .grokignore file in their repository to tell Grok what to ignore.

Describe the solution you'd like
A file that lives inside the repository (such as .grokignore) that gets read by the indexer, and causes the indexer to ignore any files in the repository that match lines in that file.

Describe alternatives you've considered
The alternative is the ignore switch on the indexer itself, but that is a server-side change, and would require relaunching of our service image - doable but not tennable.

[vladak]

If this is done, surely it will not be configurable via a dot file. We departed from these quite a long time ago. This should be a per project tunable - see https://github.com/oracle/opengrok/wiki/Per-project-configuration

[sagarkhushalani]

Unfortunately, that's still server side configuration. What I was hoping for was something that could be controlled by project teams, and could be done without any input from server administrators or require a server/service restart.

[vladak]

The architecture is very centralist; one reason is history, another is security - OpenGrok is deployed in places which require stringent controls.

[vladak]

A workaround would be to use per project workflow and assemble the command line using the dot files yourself - i.e. the dot files would contain list of ignore patterns and a script would convert them to the -i options of the indexer command line for particular project.

[vladak]

Another way how to approach the enhancement would be to allow -i to specify a project for which is the ignore pattern valid. This would still require some sort of processing on your side.