Browsing Czech translation

4989.

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later -->
<!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. -->
<h3>Index name</h3>

<p>This is the name of the Elasticsearch index that will be used by the search functionality of the site. It is unlikely that you will need to change this from its default value unless you are using the same Elasticsearch cluster as an index
for multiple Mahara sites, or if you have done a reindex using the "Bypass index"
setting.</p>
<p>If you change this to a new value, you may need to use the "reset ALL indexes"
button to trigger the creation of the new index.</p>
<p>This setting cannot be changed through the web interface. You may change it by setting a value in your config.php file for the following config variable:</p>
<p><code>$cfg->plugin->search->elasticsearch->indexname</code>.</p>

4990.

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later -->
<!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. -->
<h3>Auth password</h3>

<p>If your Elasticsearch server requires an HTTP basic auth username and password to access it, you may provide the <strong>password</strong> here. <strong>Note:</strong> The core Elasticsearch software itself does not provide username or password features, but you may achieve this functionality by using a plugin or by accessing it through a proxy.</p>
<p>This setting cannot be changed through the web interface. You may change it by setting a value in your config.php file for the following config variable:</p>
<p><code>$cfg->plugin->search->elasticsearch->password</code>.</p>

4991.

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later -->
<!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. -->
<h3>Elasticsearch port</h3>

<p>The port number to access the Elasticsearch server on.</p>
<p>This setting cannot be changed through the web interface. You may change it by setting a value in your config.php file for the following config variable:</p>
<p><code>$cfg->plugin->search->elasticsearch->port</code>.</p>

4992.

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later -->
<!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. -->
<h3>Elasticsearch search types</h3>

<p>This is a comma-separated list of the elements to index. Each of these must match an ElasticsearchType subclass under search/elasticsearch/type.</p>
<p>You shouldn't need to change this unless you have implemented a new search type, or want to disable a particular search type.</p>
<p>This setting cannot be changed through the web interface. You may change it by setting a value in your config.php file for the following config variable:</p>
<p><code>$cfg->plugin->search->elasticsearch->types</code>.</p>

4993.

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later -->
<!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. -->
<h3>Auth username</h3>

<p>If your Elasticsearch server requires an HTTP basic auth username and password to access it, you may provide the <strong>username</strong> here. <strong>Note:</strong> The core Elasticsearch software itself does not provide username or password features, but you may achieve this functionality by using a plugin or by accessing it through a proxy.</p>
<p>This setting cannot be changed through the web interface. You may change it by setting a value in your config.php file for the following config variable:</p>
<p><code>$cfg->plugin->search->elasticsearch->username</code>.</p>

4994.

Administrator

4995.

All

4996.

Elasticsearch analyzer

4997.

The Elasticsearch analyzer class to use. Default is mahara_analyzer.

4998.

Check the artefact types you want to include in the index. Only artefact types that have a hierarchy defined are valid. You will need to reset artefacts in the queue for your changes to take effect.