VuFind stores all of its configuration in plain INI files located underDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/vufind-org/vufind/llms.txt
Use this file to discover all available pages before exploring further.
config/vufind/. Every aspect of the system — from the site title and session storage to which ILS driver is loaded and how searches are ranked — is controlled by one of these files. You never edit the defaults in place; instead, you copy individual files into a local/ directory where your changes are isolated from upstream updates and survive version upgrades intact.
How the configuration system works
VuFind resolves configuration files through a layered override chain. When the application needs a setting it looks, in order, at:$VUFIND_LOCAL_DIR/config/vufind/<file>.ini— your local overrides (highest priority)$VUFIND_HOME/config/vufind/<file>.ini— the distribution defaults (fallback)
The environment variable
VUFIND_LOCAL_DIR defaults to $VUFIND_HOME/local. You can point it to a different path — for example, a directory outside the VuFind source tree — to keep your configuration entirely separate from the application code.Overriding a configuration file
Locate the default file
Find the file you want to customize in
$VUFIND_HOME/config/vufind/. For example, to change search settings, the file is searches.ini.Edit only the sections you need
Open the local copy and modify the relevant keys. You can safely delete sections you are not changing — they will be inherited from the distribution defaults.
Key configuration files
The table below maps each major configuration file to the area it controls.| File | Controls |
|---|---|
config.ini | Site identity, session, authentication method, Solr connection, ILS driver, mail, database |
searches.ini | Search handlers, sorting, results per page, recommendations, spelling |
searchspecs.yaml | Field weights, Dismax/eDismax parameters, munge rules for each search type |
facets.ini | Facet fields, facet labels, date-range facets, hierarchical facets |
permissions.ini | Role-based access control — IP ranges, Shibboleth attributes, named roles |
RecordTabs.ini | Which tabs appear on the full record view and in what order |
KohaRest.ini / Folio.ini / Alma.ini | Driver-specific settings for the respective ILS |
Shibboleth.ini | Per-IdP attribute overrides for federated login |
NoILS.ini | Behaviour when no ILS is connected or the ILS is in maintenance mode |
sms.ini | SMS carrier gateway configuration for the “Text this” feature |
CookieConsent.yaml | Cookie consent categories, GDPR compliance settings |
config.ini — the main configuration file
config.ini is the first file to customize for any new installation. Its most commonly edited sections are:
[Site] — Sets the public-facing URL, site title, default theme, language, timezone, and display date/time formats.
[Index] — Points VuFind at its Solr instance and sets the default bibliographic core.
[Authentication] — Selects the login mechanism. See Authentication for all options.
[Catalog] — Selects the ILS driver. See ILS Drivers for all options.
[Database] — Database connection string used by VuFind’s own user database.
[Mail] — SMTP settings for outbound email (password resets, saved-search notifications, etc.).
Explore configuration areas
Search Configuration
Configure Solr backends, search handlers, sorting options, results per page, field boosting, and faceted navigation.
Authentication
Set up Database, LDAP, Shibboleth, CAS, ILS-native, or OpenID Connect login methods — including multi-auth setups.
ILS Drivers
Connect VuFind to Koha, FOLIO, Alma, Sierra, Voyager, Symphony, and many more integrated library systems.
Permissions
Control access to admin panels, staff views, and gated content using IP ranges, roles, and Shibboleth attributes.
