Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode
RhodeCode Enterprise 5.6.1 documentation
RhodeCode
Enterprise 5.6.1 docs

Documentation directory

  • Back to documentation directory

RhodeCode RCstack Documentation

  • RhodeCode RCstack Installer

Admin Documentation

  • Quick Start Installation Guide
  • Supported Databases
    • MySQL or MariaDB
    • PostgreSQL
    • SQLite (Deprecated)
  • Post Installation Tasks
    • Set up Email
    • Configure Celery
    • Migrating repositories
    • Change database connection details
  • System Overview
  • System Administration
    • Configuration Files Overview
    • VCS Server Management
    • Subversion With Write Over HTTP
    • Subversion Enabling Path Permissions
    • Gunicorn SSL support
    • Apache HTTP Server Configuration
      • Apache Configuration Example
      • Diffie-Hellman Security
      • Apache URL Prefix Configuration
      • Apache WSGI Configuration
    • Nginx HTTP Server Configuration
      • Nginx Configuration Example
      • Diffie-Hellman Security
      • Nginx Proxy Config
      • Nginx URL Prefix Configuration
    • Backup and Restore
    • Tuning RhodeCode Enterprise
      • Configure Gunicorn Workers
      • Gunicorn Gevent Backend
      • VCSServer Memory Usage
      • RhodeCode Memory Usage
      • User Session Performance
      • Database Performance
      • Scale Horizontally / RhodeCode Cluster
      • Mount Cache Folders To Memory
      • Move tmp to TMPFS
      • Change Default Encoding
      • Mercurial Large Files Location
      • Git LFS storage Location
      • Mercurial Authentication Tuning
    • Full-text Search
    • Settings Management
    • Enabling Debug Mode
    • One-time Admin Tasks
    • RhodeCode Tools Clean Up Commands
    • Apply license from ishell
  • User Administration
    • Public Access
    • Default User Permissions
    • Anonymous Users
    • Adding Users
    • Setting Default Permissions
    • Setting User Group Permissions
    • Common Admin Tasks for Users
  • Repository Administration
    • Setting Repository Permissions
    • Setting Repository Group Permissions
    • Repository Extra Fields
    • RhodeCode Enterprise Repository Hooks
    • Repository Issue Tracker
    • Repository VCS Settings
    • Restoring Deleted Repositories
    • Common Admin Tasks for Repositories
  • Security Tips
    • Securing Your Server
    • Securing HTTPS Connections
    • 3 Basic User Security Steps
    • Setting IP Restrictions
    • Securing Your Server via Sophos UTM 9
  • Authentication Options
    • Authentication Tokens
    • LDAP/AD
      • Active Directory
      • LDAP / Active Directory Glossary
    • LDAP/AD With User Groups Sync
      • Active Directory
      • LDAP / Active Directory Glossary
    • SAML 2.0 Authentication
      • SAML 2.0 with Duo Security
      • SAML 2.0 with One Login
      • SAML 2.0 with Azure Entra ID
      • Bulk enroll multiple existing users
    • SAML 2.0 with One Login
    • SAML 2.0 with Duo Security
    • SAML 2.0 with Azure Entra ID
    • Crowd
    • PAM
    • SSH Connection
  • Issue Tracker Integration
  • Lab Settings

Feature Documentation

  • Collaboration
    • Workflow Support
      • Forking Workflow
      • Branching Workflow
    • Forking and Branching
    • Repository Locking
  • Notifications
    • Notifications Overview
    • Using Notifications
    • Pull Request Notifications
    • Commit Message Notifications
  • Pull Requests
    • Pull Request Workflow
    • Pull request management
    • Open a pull request
    • Review a pull request
    • Update a pull request
    • Approve pull requests
    • Merge a pull request
    • Merging Forks with an Empty Repository
  • Code Review
    • Reviewing Diffs
    • Reviewing Changes
    • Side-By-Side Diffs
    • Notifying Users
    • Approve Code Changes
    • Code Review - Best Practices
  • Integrations
    • Slack integration
    • Redmine integration
    • JIRA integration
    • Webhook integration
    • Email integration
    • CI Server integration
    • Jenkins integration
    • rcextensions integrations

User Documentation

  • Basic Usage
    • File Management
    • Repository Functions
    • Importing a repository
    • Online Editing
      • File Editing
      • Gist Editing
    • Getting Started with VCS
      • Mercurial Getting Started
      • Git Getting Started
    • Keyboard Shortcuts
  • RhodeCode Enterprise Tutorials
    • Deploy RhodeCode Enterprise From a Hosted Server
    • Mercurial Large Files Extension
    • Git LFS Extension
    • Scaling RhodeCode Enterprise Using Multiple Instances
    • Scaling Best Practices
    • How to Squash Commits in Mercurial
    • How to Squash Commits in Git
    • How to Rebase in Mercurial
    • How to Rebase in Git
    • API Example Usage
    • Merging in Mercurial
    • Mercurial Branching Vs Bookmarking
    • Moving From Windows to Linux
    • Collaboration Best Practices

Developer Documentation

  • API Documentation
    • repo methods
    • store methods
    • license methods
    • deprecated methods
    • gist methods
    • pull_request methods
    • repo_group methods
    • search methods
    • server methods
    • user methods
    • user_group methods
  • RhodeCode Tools
    • RhodeCode Tools Overview
    • RhodeCode Tools Installation
    • RhodeCode Tools CLI
    • rhodecode-list-instances
    • rhodecode-tools
    • rhodecode-api
    • rhodecode-cleanup-gists
    • rhodecode-cleanup-repos
    • rhodecode-config
    • rhodecode-extensions
    • rhodecode-gist
    • rhodecode-index
    • rhodecode-setup-config
  • Extensions & Hooks
  • Contributing to RhodeCode
    • Contributing Overview
    • Testing and Specifications
      • Unit and Functional Tests
      • Specification by Example
      • Naming conventions
    • Development setup
    • DB Schema and Migration
    • Settings for Development
    • CONTRIBUTING TO API
    • Dependency management
    • Ticket Checklists
    • Pull Request Checklists
    • Code style and structure guide for frontend work
    • Contribution Standards

RhodeCode rcstack Documentation

  • RhodeCode Installer

About

  • Release Notes
    • RhodeCode Enterprise 5.6.1 Release Notes
    • RhodeCode Enterprise 5.6.0 Release Notes
    • RhodeCode Enterprise 5.5.3 Release Notes
    • RhodeCode Enterprise 5.5.2 Release Notes
    • RhodeCode Enterprise 5.5.1 Release Notes
    • RhodeCode Enterprise 5.5.0 Release Notes
    • RhodeCode Enterprise 5.4.2 Release Notes
    • RhodeCode Enterprise 5.4.1 Release Notes
    • RhodeCode Enterprise 5.4.0 Release Notes
    • RhodeCode Enterprise 5.3.1 Release Notes
    • RhodeCode Enterprise 5.3.0 Release Notes
    • RhodeCode Enterprise 5.2.1 Release Notes
    • RhodeCode Enterprise 5.2.0 Release Notes
    • RhodeCode Enterprise 5.1.2 Release Notes
    • RhodeCode Enterprise 5.1.1 Release Notes
    • RhodeCode Enterprise 5.1.0 Release Notes
    • RhodeCode Enterprise 5.0.3 Release Notes
    • RhodeCode Enterprise 5.0.2 Release Notes
    • RhodeCode Enterprise 5.0.1 Release Notes
    • RhodeCode Enterprise 5.0.0 Release Notes
    • RhodeCode Enterprise 4.27.1 Release Notes
    • RhodeCode Enterprise 4.27.0 Release Notes
    • RhodeCode Enterprise 4.26.0 Release Notes
    • RhodeCode Enterprise 4.25.2 Release Notes
    • RhodeCode Enterprise 4.25.1 Release Notes
    • RhodeCode Enterprise 4.25.0 Release Notes
    • RhodeCode Enterprise 4.24.1 Release Notes
    • RhodeCode Enterprise 4.24.0 Release Notes
    • RhodeCode Enterprise 4.23.2 Release Notes
    • RhodeCode Enterprise 4.23.1 Release Notes
    • RhodeCode Enterprise 4.23.0 Release Notes
    • RhodeCode Enterprise 4.22.0 Release Notes
    • RhodeCode Enterprise 4.21.0 Release Notes
    • RhodeCode Enterprise 4.20.1 Release Notes
    • RhodeCode Enterprise 4.20.0 Release Notes
    • RhodeCode Enterprise 4.19.3 Release Notes
    • RhodeCode Enterprise 4.19.2 Release Notes
    • RhodeCode Enterprise 4.19.1 Release Notes
    • RhodeCode Enterprise 4.19.0 Release Notes
    • RhodeCode Enterprise 4.18.3 Release Notes
    • RhodeCode Enterprise 4.18.2 Release Notes
    • RhodeCode Enterprise 4.18.1 Release Notes
    • RhodeCode Enterprise 4.18.0 Release Notes
    • RhodeCode Enterprise 4.17.4 Release Notes
    • RhodeCode Enterprise 4.17.3 Release Notes
    • RhodeCode Enterprise 4.17.2 Release Notes
    • RhodeCode Enterprise 4.17.1 Release Notes
    • RhodeCode Enterprise 4.17.0 Release Notes
    • RhodeCode Enterprise 4.16.2 Release Notes
    • RhodeCode Enterprise 4.16.1 Release Notes
    • RhodeCode Enterprise 4.16.0 Release Notes
    • RhodeCode Enterprise 4.15.2 Release Notes
    • RhodeCode Enterprise 4.15.1 Release Notes
    • RhodeCode Enterprise 4.15.0 Release Notes
    • RhodeCode Enterprise 4.14.1 Release Notes
    • RhodeCode Enterprise 4.14.0 Release Notes
    • RhodeCode Enterprise 4.13.3 Release Notes
    • RhodeCode Enterprise 4.13.2 Release Notes
    • RhodeCode Enterprise 4.13.1 Release Notes
    • RhodeCode Enterprise 4.13.0 Release Notes
    • RhodeCode Enterprise 4.12.4 Release Notes
    • RhodeCode Enterprise 4.12.3 Release Notes
    • RhodeCode Enterprise 4.12.2 Release Notes
    • RhodeCode Enterprise 4.12.1 Release Notes
    • RhodeCode Enterprise 4.12.0 Release Notes
    • RhodeCode Enterprise 4.11.6 Release Notes
    • RhodeCode Enterprise 4.11.5 Release Notes
    • RhodeCode Enterprise 4.11.4 Release Notes
    • RhodeCode Enterprise 4.11.3 Release Notes
    • RhodeCode Enterprise 4.11.2 Release Notes
    • RhodeCode Enterprise 4.11.1 Release Notes
    • RhodeCode Enterprise 4.11.0 Release Notes
    • RhodeCode Enterprise 4.10.6 Release Notes
    • RhodeCode Enterprise 4.10.5 Release Notes
    • RhodeCode Enterprise 4.10.4 Release Notes
    • RhodeCode Enterprise 4.10.3 Release Notes
    • RhodeCode Enterprise 4.10.2 Release Notes
    • RhodeCode Enterprise 4.10.1 Release Notes
    • RhodeCode Enterprise 4.10.0 Release Notes
    • RhodeCode Enterprise 4.9.1 Release Notes
    • RhodeCode Enterprise 4.9.0 Release Notes
    • RhodeCode Enterprise 4.8.0 Release Notes
    • RhodeCode Enterprise 4.7.2 Release Notes
    • RhodeCode Enterprise 4.7.1 Release Notes
    • RhodeCode Enterprise 4.7.0 Release Notes
    • RhodeCode Enterprise 4.6.1 Release Notes
    • RhodeCode Enterprise 4.6.0 Release Notes
    • RhodeCode Enterprise 4.5.2 Release Notes
    • RhodeCode Enterprise 4.5.1 Release Notes
    • RhodeCode Enterprise 4.5.0 Release Notes
    • RhodeCode Enterprise 4.4.2 Release Notes
    • RhodeCode Enterprise 4.4.1 Release Notes
    • RhodeCode Enterprise 4.4.0 Release Notes
    • RhodeCode Enterprise 4.3.1 Release Notes
    • RhodeCode Enterprise 4.3.0 Release Notes
    • RhodeCode Enterprise 4.2.1 Release Notes
    • RhodeCode Enterprise 4.2.0 Release Notes
    • RhodeCode Enterprise 4.1.2 Release Notes
    • RhodeCode Enterprise 4.1.1 Release Notes
    • RhodeCode Enterprise 4.1.0 Release Notes
    • RhodeCode Enterprise 4.0.1 Release Notes
    • RhodeCode Enterprise 4.0.0 Release Notes
    • RhodeCode Enterprise 3.8.4 Release Notes
    • RhodeCode Enterprise 3.8.3 Release Notes
    • RhodeCode Enterprise 3.8.2 Release Notes
    • RhodeCode Enterprise 3.8.1 Release Notes
    • RhodeCode Enterprise 3.8.0 Release Notes
    • RhodeCode Enterprise 3.7.1 Release Notes
    • RhodeCode Enterprise 3.7.0 Release Notes
    • RhodeCode Enterprise 3.6.1 Release Notes
    • RhodeCode Enterprise 3.6.0 Release Notes
    • RhodeCode Enterprise 3.5.2 Release Notes
    • RhodeCode Enterprise 3.5.1 Release Notes
    • RhodeCode Enterprise 3.5.0 Release Notes
    • RhodeCode Enterprise 3.4.1 Release Notes
    • RhodeCode Enterprise 3.4.0 Release Notes
    • RhodeCode Enterprise 3.3.4 Release Notes
    • RhodeCode Enterprise 3.3.3 Release Notes
    • RhodeCode Enterprise 3.3.2 Release Notes
    • RhodeCode Enterprise 3.3.1 Release Notes
    • RhodeCode Enterprise 3.3.0 Release Notes
    • RhodeCode Enterprise 3.2.3 Release Notes
    • RhodeCode Enterprise 3.2.2 Release Notes
    • RhodeCode Enterprise 3.2.1 Release Notes
    • RhodeCode Enterprise 3.2.0 Release Notes
    • RhodeCode Enterprise 3.1.1 Release Notes
    • RhodeCode Enterprise 3.1.0 Release Notes
    • RhodeCode Enterprise 3.0.2 Release Notes
    • RhodeCode Enterprise 3.0.1 Release Notes
    • RhodeCode Enterprise 3.0.0 Release Notes
    • RhodeCode Enterprise 2.2.8 Release Notes
    • RhodeCode Enterprise 2.2.7 Release Notes
    • RhodeCode Enterprise 2.2.6 Release Notes
    • RhodeCode Enterprise 2.2.5 Release Notes
    • RhodeCode Enterprise 2.2.4 Release Notes
    • RhodeCode Enterprise 2.2.3 Release Notes
    • RhodeCode Enterprise 2.2.2 Release Notes
    • RhodeCode Enterprise 2.2.1 Release Notes
    • RhodeCode Enterprise 2.2.0 Release Notes
    • RhodeCode Enterprise 2.1.0 Release Notes
    • RhodeCode Enterprise 2.0.2 Release Notes
    • RhodeCode Enterprise 2.0.1 Release Notes
    • RhodeCode Enterprise 2.0.0 Release Notes
    • RhodeCode Enterprise 1.7.2 Release Notes
    • RhodeCode Enterprise 1.7.1 Release Notes
    • RhodeCode Enterprise 1.7.0 Release Notes
    • RhodeCode Enterprise 1.6.0 Release Notes
  • Known Issues
  • Glossary
Back to top

Full-text Search¶

RhodeCode provides a full text search capabilities to search inside file content, commit message, and file paths (This feature is only available in Enterprise edition). Indexing is not enabled by default and to use full text search building an index is a pre-requisite.

RhodeCode Enterprise provides support for ElasticSearch 8 as a backend to index repositories. See Enabling ElasticSearch for details.

Indexing¶

To run the indexer you need to have an generated 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 force option in the configuration file, or run it with –force flag.

Important

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:

  1. Configure the .rhoderc File, if running tools remotely.

  2. Run the Indexer

  3. Schedule the Indexer

  4. Advanced Indexing

Configure the .rhoderc File¶

Note

Optionally it’s possible to use indexer without the .rhoderc. Simply instead of executing with –instance-name=rcstack-instance 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.

# Get the status of each instance you wish to use with Tools
$ ./rcstack status

RCSTACK: v5.27.3, running hostname: http://code.rhodecode.com

To get your API Token, on the RhodeCode Enterprise interface go to username ‣ My Account ‣ Auth tokens

Given we’re running rcstack, lets create the configuration file using docker mounts

./rcstack cli cmd rhodecode-tools setup-config \
--filename=/vol/confvolume/.rhoderc \
--instance-name=rcstack-instance \
api_host=https://code.rhodecode.com,api_key=secret-api-key

Let’s verify created config using list-instances command

./rcstack cli cmd rhodecode-tools  list-instances --config=/vol/confvolume/.rhoderc
*Volumes*:
 attaching /mnt/mac/Users/marcin/workspace/rhodecode-enterprise-docker/config/_shared               under: /vol/confvolume

ENTRYPOINT: Running rhodecode_vcsserver with cmd 'rhodecode-tools'
checking if config files needs bootstrapping

[instance:rcstack-instance] - Config only
  API-HOST: https://code.rhodecode.com
  API-KEY:  secret-api-key

This is how the file should look like

# Configure .rhoderc with matching details
# This allows the indexer to connect to the instance
[instance:rcstack-instance]
api_host = http://code.rhodecode.com
api_key = secret-api-key

Run the Indexer¶

Run the indexer using the following command, and specify the instance you want to index against:

# Using default simples indexing of all repositories
./rcstack cli cmd rhodecode-index \
--config=/vol/confvolume/.rhoderc \
--instance-name=rcstack-instance \
--engine-location=http://elasticsearch-host:9200

# Create a custom mapping (search_mapping.ini) rules file for detailed indexing invocation
./rcstack cli cmd rhodecode-index \
--config=/vol/confvolume/.rhoderc \
--instance-name=rcstack-instance \
--create-mapping=/vol/confvolume/search_mapping.ini

# Using a custom mapping file with indexing rules
./rcstack cli cmd rhodecode-index \
--config=/vol/confvolume/.rhoderc \
--instance-name=rcstack-instance \
--engine-location=http://elasticsearch-host:9200 \
--mapping=/vol/confvolume/search_mapping.ini

Schedule the Indexer¶

To schedule the indexer, configure the crontab file to run the indexer inside your RhodeCode Tools virtualenv using the following steps.

  1. Open the crontab file, using crontab -e.

  2. Add the indexer to the crontab, and schedule it to run as regularly as you wish.

  3. 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 * * * <CMD FOR INDEXING GOES HERE>

# Run the indexer every Sunday at 3am using default mapping
* 3 * * 0 <CMD FOR INDEXING GOES HERE>

# Run the indexer every 15 minutes
# using a specially configured mapping file
*/15 * * * * <CMD FOR INDEXING GOES HERE>

Advanced Indexing¶

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:

./rcstack cli cmd rhodecode-index --instance-name=rcstack-instance --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:

./rcstack cli cmd rhodecode-index --instance-name=rcstack-instance --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.

Note

If you need to create the search_mapping.ini file manually, use the RhodeCode Tools ./rcstack cli cmd rhodecode-index --create-mapping=path/to/search_mapping.ini call. For details, see the RhodeCode Tools CLI section.

To Run the indexer with mapping file provide it using –mapping flag:

./rcstack cli cmd rhodecode-index --instance-name=rcstack-instance --mapping=/my/path/search_mapping.ini

Here’s a detailed example of using search_mapping.ini file.

[__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:

./rcstack cli cmd rhodecode-index --instance-name=rcstack-instance --show-matched-repos --mapping=/my/path/search_mapping.ini
Next
Settings Management
Previous
Mercurial Authentication Tuning
Copyright © 2010-2025, RhodeCode GmbH
Last updated on 16:07 Jul 17, 2025
Got documentation defects and suggestions? Submit docs issues
On this page
  • Full-text Search
    • Indexing
    • Configure the .rhoderc File
    • Run the Indexer
    • Schedule the Indexer
    • Advanced Indexing
      • Force Re-Indexing single repository
      • Removing repositories from index
      • Using search_mapping.ini file for advanced index rules