Solr is highly reliable, scalable and fault tolerant, providing distributed indexing, replication and load-balanced querying, automated failover and recovery, centralized configuration and more. Solr powers the search and navigation features of many of the world's largest internet sites.
- Supported versions
- Legacy versions
- Patch versions
- Getting information
- Additional Reading
You can still run these versions with Lando but for all intents and purposes they should be considered deprecated eg YMMV and do not expect a ton of support if you have an issue.
Not officially supported!
While we allow users to specify patch versions for this service they are not officially supported so if you use one YMMV. Also note that patch versions are not available for Solr 3.x and 4.x
To use a patch version you can do something like this:
services: my-service: type: solr:5.5.5
But make sure you use one of the available patch tags for the underlying image we are using.
Here are the configuration options, set to the default values, for this service. If you are unsure about where this goes or what this means we highly recommend scanning the services documentation to get a good handle on how the magicks work.
services: my-service: type: solr:7 portforward: false core: lando config: dir: SEE BELOW
portforward will allow you to access this service externally by given you a port directly on your host's
localhost. Note that
portforward can be set to either
true or a specific
port but we highly recommend you set it to
true unless you have pretty good knowledge of how port assignment works or you have a very compelling reason for needing a locked down port.
portforward: true will prevent inevitable port collisions and provide greater reliability and stability across Lando apps. That said, one downside of
portforward: true is that Docker will assign a different port every time you restart your application. You can read more about accessing services externally over here.
services: my-service: type: solr portforward: true
services: my-service: type: solr portforward: 8983
You can easily set up a different core name with the
core cofig value
services: my-service: type: solr core: my-core
Solr 5+ only
core config value does not work for Solr 3.x or 4.x
You will almost certainly need to utilize your own custom Solr config. You can do that by telling Lando to inject solr config from a directory inside of your application.
Consider the below example of a Drupal 8 application injecting the Solr 7.x config directly from the
A hypothetical project
Note that you can put your configuration files anywhere inside your application directory. We use a
config directory in the below example but you can call it whatever you want such as
./ |-- sites/all/modules/search_api_solr/solr-conf/7.x |-- elevate.xml |-- mapping-ISOLatin1Accent.txt |-- protwords.txt |-- schema_extra_fields.xml |-- schema_extra_types.xml |-- schema.xml |-- solrconfig_extra.xml |-- solrconfig_index.xml |-- solrconfig_spellcheck.xml |-- solrconfig.xml |-- solrcore.properties |-- stopwords.txt |-- synonyms.txt |-- .lando.yml
Landofile's solr config
services: my-service: type: solr config: dir: sites/all/modules/search_api_solr/solr-conf/7.x
If you are interested in a working example of this service that we test on every Lando build then check out https://github.com/lando/lando/tree/master/examples/solr
- Updating your Landofiles to 3.0.0-rc.2+
- Accessing Your Services Externally
- Accessing Lando from Other Devices
- Exporting Databases
- Importing Databases
- Killer D8 Workflow with Platform.sh
- Lando + PhpStorm + Xdebug
- Offline Development
- Using $LANDO_INFO
- Using NodeJS Frontend Tooling
- Using Lando in Visual Studio Code
- Climbing a mountain for love
- SSH Keys
- Shared Files
- Global Config
- DNS Rebinding Protection
- File Uploads on Windows
- File Syncing Stalled
- Running VB and HyperV
- Running behind a proxy
- Switching Database Config