RhodeCode provides a full text search capabilities to search inside file content, commit message, and file paths. Indexing is not enabled by default and to use full text search building an index is a pre-requisite.
By default RhodeCode is configured to use Whoosh to index repositories and provide full-text search. Whoosh works well for a small amount of data and shouldn’t be used in case of large code-bases and lots of repositories.
To run the indexer you need to have an Authentication Token with admin rights to all repositories.
To index repositories stored in RhodeCode, you have the option to set the indexer up in a number of ways, for example:
- Call the indexer via a cron job. We recommend running this once at night. In case you need everything indexed immediately it’s possible to index few times during the day. Indexer has a special locking mechanism that won’t allow two instances of indexer running at once. It’s safe to run it even every 1hr.
- Set the indexer to infinitely loop and reindex as soon as it has run its previous cycle.
- Hook the indexer up with your CI server to reindex after each push.
The indexer works by indexing new commits added since the last run, and comparing
file changes to index only new or modified files.
If you wish to build a brand new index from scratch each time, use the
option in the configuration file, or run it with –force flag.
You need to have RhodeCode Tools installed, see RhodeCode Tools Installation. Since RhodeCode Enterprise 3.5.0 they are installed by default and available with community/enterprise installations.
To set up indexing, use the following steps:
Optionally it’s possible to use indexer without the
.rhoderc. Simply instead of
executing with –instance-name=enterprise-1 execute providing the host and token
directly: –api-host=http://127.0.0.1:10000 –api-key=<auth-token-goes-here>
RhodeCode Tools uses the
/home/user/.rhoderc file for connection details
to RhodeCode Enterprise instances. If this file is not automatically created,
you can configure it using the following example. You need to configure the
details for each instance you want to index.
# Check the instance details # of the instance you want to index $ rccontrol status - NAME: enterprise-1 - STATUS: RUNNING - TYPE: Enterprise - VERSION: 4.1.0 - URL: http://127.0.0.1:10003
To get your API Token, on the RhodeCode Enterprise interface go to
# Configure .rhoderc with matching details # This allows the indexer to connect to the instance [instance:enterprise-1] api_host = http://127.0.0.1:10000 api_key = <auth token goes here>
Run the Indexer¶
Run the indexer using the following command, and specify the instance you want to index:
# Using default simples indexing of all repositories $ /home/user/.rccontrol/enterprise-1/profile/bin/rhodecode-index \ --instance-name=enterprise-1 # Using a custom mapping file with indexing rules, and using elasticsearch 6 backend $ /home/user/.rccontrol/enterprise-1/profile/bin/rhodecode-index \ --instance-name=enterprise-1 \ --mapping=/home/user/.rccontrol/enterprise-1/search_mapping.ini \ --es-version=6 --engine-location=http://elasticsearch-host:9200 # Using a custom mapping file and invocation without ``.rhoderc`` $ /home/user/.rccontrol/enterprise-1/profile/bin/rhodecode-index \ --api-host=http://rhodecodecode.myserver.com --api-key=xxxxx \ --mapping=/home/user/.rccontrol/enterprise-1/search_mapping.ini # From inside a virtualev on your local machine or CI server. (venv)$ rhodecode-index --instance-name=enterprise-1
In case of often indexing the index may become fragmented. Most often a result of that is error about too many open files. To fix this indexer needs to be executed with –optimize flag. E.g rhodecode-index –instance-name=enterprise-1 –optimize This should be executed regularly, once a week is recommended.
Schedule the Indexer¶
To schedule the indexer, configure the crontab file to run the indexer inside your RhodeCode Tools virtualenv using the following steps.
- Open the crontab file, using
- Add the indexer to the crontab, and schedule it to run as regularly as you wish.
- Save the file.
$ crontab -e # The virtualenv can be called using its full path, so for example you can # put this example into the crontab # Run the indexer daily at 4am using the default mapping settings * 4 * * * /home/ubuntu/.virtualenv/rhodecode-venv/bin/rhodecode-index \ --instance-name=enterprise-1 # Run the indexer every Sunday at 3am using default mapping * 3 * * 0 /home/ubuntu/.virtualenv/rhodecode-venv/bin/rhodecode-index \ --instance-name=enterprise-1 # Run the indexer every 15 minutes # using a specially configured mapping file */15 * * * * ~/.rccontrol/enterprise-4/profile/bin/rhodecode-index \ --instance-name=enterprise-4 \ --mapping=/home/user/.rccontrol/enterprise-4/search_mapping.ini
Force Re-Indexing single repository¶
Often it’s required to re-index whole repository because of some repository changes, or to remove some indexed secrets, or files. There’s a special –repo-name= flag for the indexer that limits execution to a single repository. For example to force-reindex single repository such call can be made:
rhodecode-index --instance-name=enterprise-1 --force --repo-name=rhodecode-vcsserver
Removing repositories from index¶
The indexer automatically removes renamed repositories and builds index for new names. In the same way if a listed repository in mapping.ini is not reported existing by the server it’s removed from the index. In case that you wish to remove indexed repository manually such call would allow that:
rhodecode-index --instance-name=enterprise-1 --remove-only --repo-name=rhodecode-vcsserver
Using search_mapping.ini file for advanced index rules¶
By default rhodecode-index runs for all repositories, all files with parsing limits defined by the CLI default arguments. You can change those limits by calling with different flags such as –max-filesize=2048kb or –repo-limit=10
For more advanced execution logic it’s possible to use a configuration file that would define detailed rules which repositories and how should be indexed.
RhodeCode Tools provides an example index configuration file called
This file is created by default during installation and is located at:
/home/user/.rccontrol/instance-id/search_mapping.ini, using default RhodeCode Tools.
~/venv/lib/python2.7/site-packages/rhodecode_tools/templates/mapping.ini, when using
If you need to create the
search_mapping.ini file manually, use the RhodeCode Tools
rhodecode-index --create-mapping path/to/search_mapping.ini API call.
For details, see the RhodeCode Tools CLI section.
To Run the indexer with mapping file provide it using –mapping flag:
rhodecode-index --instance-name=enterprise-1 --mapping=/my/path/search_mapping.ini
Here’s a detailed example of using
[__DEFAULT__] ; Create index on commits data, and files data in this order. Available options ; are `commits`, `files` index_types = commits,files ; Commit fetch limit. In what amount of chunks commits should be fetched ; via api and parsed. This allows server to transfer smaller chunks and be less loaded commit_fetch_limit = 1000 ; Commit process limit. Limit the number of commits indexer should fetch, and ; store inside the full text search index. eg. if repo has 2000 commits, and ; limit is 1000, on the first run it will process commits 0-1000 and on the ; second 1000-2000 commits. Help reduce memory usage, default is 50000 ; (set -1 for unlimited) commit_process_limit = 20000 ; Limit of how many repositories each run can process, default is -1 (unlimited) ; in case of 1000s of repositories it's better to execute in chunks to not overload ; the server. repo_limit = -1 ; Default patterns for indexing files and content of files. Binary files ; are skipped by default. ; Add to index those comma separated files; globs syntax ; e.g index_files = *.py, *.c, *.h, *.js index_files = *, ; Do not add to index those comma separated files, this excludes ; both search by name and content; globs syntax ; e.g index_files = *.key, *.sql, *.xml, *.pem, *.crt skip_files = , ; Add to index content of those comma separated files; globs syntax ; e.g index_files = *.h, *.obj index_files_content = *, ; Do not add to index content of those comma separated files; globs syntax ; Binary files are not indexed by default. ; e.g index_files = *.min.js, *.xml, *.dump, *.log, *.dump skip_files_content = , ; Force rebuilding an index from scratch. Each repository will be rebuild from ; scratch with a global flag. Use --repo-name=NAME --force to rebuild single repo force = false ; maximum file size that indexer will use, files above that limit are not going ; to have they content indexed. ; Possible options are KB (kilobytes), MB (megabytes), eg 1MB or 1024KB max_filesize = 10MB [__INDEX_RULES__] ; Ordered match rules for repositories. A list of all repositories will be fetched ; using API and this list will be filtered using those rules. ; Syntax for entry: `glob_pattern_OR_full_repo_name = 0 OR 1` where 0=exclude, 1=include ; When this ordered list is traversed first match will return the include/exclude marker ; For example: ; upstream/binary_repo = 0 ; upstream/subrepo/xml_files = 0 ; upstream/* = 1 ; special-repo = 1 ; * = 0 ; This will index all repositories under upstream/*, but skip upstream/binary_repo ; and upstream/sub_repo/xml_files, last * = 0 means skip all other matches ; == EXPLICIT REPOSITORY INDEXING == ; If defined this will skip using __INDEX_RULES__, and will not use API to fetch ; list of repositories, it will explicitly take names defined with [NAME] format and ; try to build the index, to build index just for repo_name_1 and special-repo use: ; [repo_name_1] ; [special-repo] ; == PER REPOSITORY CONFIGURATION == ; This allows overriding the global configuration per repository. ; example to set specific file limit, and skip certain files for repository special-repo ; the CLI flags doesn't override the conf settings. ; [conf:special-repo] ; max_filesize = 5mb ; skip_files = *.xml, *.sql
In case of 1000s of repositories it can be tricky to write the include/exclude rules at first. There’s a special flag to test the mapping file rules and list repositories that would be indexed. Run the indexer with –show-matched-repos to list only the match repositories defined in .ini file rules:
rhodecode-index --instance-name=enterprise-1 --show-matched-repos --mapping=/my/path/search_mapping.ini
ElasticSearch is available in EE edition only. It provides much scalable and more advanced search capabilities. While Whoosh is fine for upto 1-2GB of data, beyond that amount it starts slowing down, and can cause other problems. New ElasticSearch 6 also provides much more advanced query language. It allows advanced filtering by file paths, extensions, use OR statements, ranges etc. Please check query language examples in the search field for some advanced query language usage.
- Open the
rhodecode.inifile for the instance you wish to edit. The default location is
- Find the search configuration section:
################################### ## SEARCH INDEXING CONFIGURATION ## ################################### search.module = rhodecode.lib.index.whoosh search.location = %(here)s/data/index
and change it to:
search.module = rc_elasticsearch search.location = http://localhost:9200 ## specify Elastic Search version, 6 for latest or 2 for legacy search.es_version = 6
search.location points to the ElasticSearch server
by default running on port 9200.
Index invocation also needs change. Please provide –es-version= and –engine-location= parameters to define ElasticSearch server location and it’s version. For example:
rhodecode-index --instace-name=enterprise-1 --es-version=6 --engine-location=http://localhost:9200