This release is a pre-release and may not be stable for production use.
Introduction
Buildout recipe for Solr.
Supported options
The recipe supports the following options:
- src (required)
Source of the Solr download (e.g. “http://archive.apache.org/dist/lucene/solr/7.7.2/solr-7.7.2.zip”).
- port (default: 8983)
Solr port
- solr-config
Path to a Solr configuration directory that contains a “core.properties” file and a “data” and “conf” directory.
- solr-core-name (default: plone)
Name of the Solr core. Default is ‘plone’.
Example usage
Minimal Buildout
We’ll start by creating a minimal buildout that uses the recipe:
>>> write('buildout.cfg',
... """
... [buildout]
... parts = solr
...
... [solr]
... recipe = kitconcept.recipe.solr
... src = %(src)s
... """ % {
... 'src' : 'http://archive.apache.org/dist/lucene/solr/7.7.2/solr-7.7.2.zip',
... })
The only required attribute is src that contains a URL of the Solr tgz file.
Running the buildout gives us:
>>> buildout_output_lower = system(buildout).lower() >>> "installing solr" in buildout_output_lower True >>> import os >>> current_path = os.path.dirname(os.path.realpath(__file__)) >>> full_path = os.path.join(current_path, 'parts/solr/bin/solr') >>> os.path.exists(full_path) True >>> full_path = os.path.join(current_path, 'parts/solr/server/solr/plone') >>> os.path.exists(full_path) True
Complete Buildout
We’ll start by creating a buildout that uses the recipe:
>>> write('buildout.cfg',
... """
... [buildout]
... parts = solr
...
... [solr]
... recipe = kitconcept.recipe.solr
... src = %(src)s
... port = %(port)s
... solr-config = %(solr-config)s
... solr-core-name = %(solr-core-name)s
... """ % {
... 'src' : 'http://archive.apache.org/dist/lucene/solr/7.7.2/solr-7.7.2.zip',
... 'port' : '8983',
... 'solr-config': 'config',
... 'solr-core-name': 'solr-core-plone',
... })
Running the buildout gives us:
>>> buildout_output_lower = system(buildout).lower() >>> "installing solr" in buildout_output_lower True >>> import os >>> current_path = os.path.dirname(os.path.realpath(__file__)) >>> full_path = os.path.join(current_path, 'parts/solr/bin/solr') >>> os.path.exists(full_path) True >>> full_path = os.path.join(current_path, 'parts/solr/server/solr/plone') >>> os.path.exists(full_path) True
Detailed Documentation
Contributors
- Note: place names and roles of the people who contribute to this package
in this file, one to a line, like so:
Timo Stollenwerk (kitconcept GmbH)
Change history
Changelog
1.0.0a4 (2019-12-23)
Use configured port in solr-forground [csenger]
1.0.0a3 (2019-03-23)
Fix README.rst. [kitconcept]
1.0.0a2 (2019-03-23)
Make config variable optional. [kitconcept]
1.0.0a1 (2019-02-07)
Initial release. [kitconcept]
Download
Metadata
Release files for kitconcept.recipe.solr 1.0.0a5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| kitconcept.recipe.solr-1.0.0a5.tar.gz | 39.9 kB | Without provenance | Details for kitconcept.recipe.solr-1.0.0a5.tar.gz |
Release files / kitconcept.recipe.solr-1.0.0a5.tar.gz
| Download URL | kitconcept.recipe.solr-1.0.0a5.tar.gz |
|---|---|
| Size | 39.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e1465d6f3732eb8a11b7784fd9764447d3bbf9766dad78aadbf9c9349a19af67
|
|
BLAKE2b-256 checksum How to use checksums |
490025f27ba0d2acd64cd13e175f6ea406d76f276deb8dbdab499293a0df6e05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/33.1.1 requests-toolbelt/0.9.1 tqdm/4.34.0 CPython/2.7.16
|
Security for kitconcept.recipe.solr 1.0.0a5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.