Page tree
Skip to end of metadata
Go to start of metadata

A Squirro cluster can be extensively configured. This section covers the available configuration options and facilities in detail.

Table of Contents

Configuration Files


Each service has its own configuration file /etc/squirro/<servicename>.ini. Additionally there is a common configuration file which applies to all services at /etc/squirro/common.ini.

  • Page:
    bing.ini — The bing.ini config file, located at /etc/squirro/bing.ini configures the workings of the Bing Provider.
  • Page:
    cluster.ini — The cluster.ini config file, located at /etc/squirro/cluster.ini configures the workings of the Cluster Service that allows to do run Squirro on multiple server.
  • Page:
    common.ini — The common.ini config file, located at /etc/squirro/common.ini configures common settings for all of the Squirro services.
  • Page:
    convert.ini — The convert.ini config file, located at /etc/squirro/convert.ini configures the content conversion.
  • Page:
    filtering.ini — The filtering.ini config file, located at /etc/squirro/filtering.ini configures the Filtering process, which is responsible for search tagging, alerts and trend updates.
  • Page:
    fingerprint.ini — The fingerprint.ini config file, located at /etc/squirro/fingerprint.ini configures the workings of the fingerprint service. That service is responsible for the management of Smart Filters.
  • Page:
    youtube.ini — The youtube.ini config file, located at /etc/squirro/youtube.ini configures the workings of the YouTube Provider.


For configuration of Elasticsearch, please refer to its documentation: Elasticsearch Configuration.


By default, on Squirro in a Box, the configuration files are managed by Puppet. Puppet is a configuration management solution. Please refer to Puppet and squirro.yaml for information about how to change configuration in that case.

  • No labels